This is indeed expected, at least at a technical level, because each snap interacts with a private view of /tmp. As a form of isolation and to avoid accidental dependencies created through data shared through /tmp, snapped applications need a better form of exchanging data. I realize that there is nothing useful that can be done about this problem for now, apart from saving the files in your home directory for round-trip between programs.
Eventually we may either build some automatic mapping for files that are operated via /tmp or said applications will benefit from improvements to platform code that manages sandboxed applications, like the portal system.
This is indeed expected, at least at a technical level, because each snap interacts with a private view of /tmp. As a form of isolation and to avoid accidental dependencies created through data shared through /tmp, snapped applications need a better form of exchanging data. I realize that there is nothing useful that can be done about this problem for now, apart from saving the files in your home directory for round-trip between programs.
Eventually we may either build some automatic mapping for files that are operated via /tmp or said applications will benefit from improvements to platform code that manages sandboxed applications, like the portal system.