'import archive' not working in 20241126 flatpak on RPI 4B

Dear forum,

i have Raspberry-PI 4B and used Jami successfully as BabyCam (using the auto-pick up setting).
But recently the snap started failing.
Since the Jami snap for RPI is outdated, i tried the newer flatpak.

I installed the flatpak according to Install Jami on Linux | Flathub and rebooted.
Running the application from the start-menu the main dialog appears.
i select ‘i already have an account’
and select ‘import from an archive backup’
and select ‘select archive file’ and select the .gzip file from my downloads folder.

if i then select ‘import’, it will show the ‘processing’ icon indefinitely.
Also when i start jami using ‘flatpak run net.jami.Jami -d’ there are no errors logged to the console.

(Also, leftclick on the jami icon in the tray, crashes/closes the app and icon. but rightclick on the tray icon does work showing the popup with ‘show jami’ and ‘quit’)

Using “flatseal” i tried giving the flatpak all permissions, but that didn’t change anything.
i’m not sure where to look next.

According to ‘flatseal’ i’m running jami flatpak

  • Version: 20241126.0
  • Last updated: November 26,2024
  • Runtime: org.kde.Platform/aarch64/6.8

Any pointers are appreciated.

Jami on servers runs on the Raspberry Pi, as only the jami-daemon and dbus-x11 are required.

The Jami client requires Qt 6.8 for the Jami GUI. Qt 6.8 does not have regular support for ARM-based hardware.

Note: For Linux on Arm on desktops, we use Raspberry Pi 5 with 8GB RAM and Ubuntu 24.04 as a reference platform. If you have an issue with another hardware, please try to reproduce the issue on Raspberry Pi 5. We plan to move to regular platform support when a wider range of ARM-based desktop hardware becomes available.

it is the same issue I have on arch: the Flatpak version is too old, client’s interface to Jami network has changed since. No one on Jami team seem to bother supporting flatpaks and stick to snaps instead, no idea why.

Note: Not a developer.

Jami can be installed with:

  • Terminal commands.
  • DEB and RPM installation files.

It is unsure why Snaps are officially supported, as dropping official support for Snaps might enable developers to allocate their time packaging Jami using Snaps to improving the Jami application.

The following image is from the Beyond APT: Software Management with Flatpak on Ubuntu | Linux Journal page.

Possible reasons the Jami team may support Snaps and not Flatpak:

  • Snaps has support for desktops, IoT (Internet of Things), and servers.
  • Snaps are harder for the community to build.
  • Flatpaks can be built by the community.
  • There is a client who requires, and pays for, Snap support.