Login credentials are not saved in Snapmaker Orca Slicer 2.2.1 (Linux Flatpak & AppImage)

[Al-hoi]

Description:
Snapmaker Orca Slicer v2.2.1 on Linux fails to save login credentials between sessions. Users must manually log in every time they start the application. This affects both Flatpak and AppImage installations.

Steps to reproduce:

Launch Snapmaker Orca Slicer 2.2.1 (Flatpak or AppImage).

Enter Snapmaker account credentials and log in successfully.

Close the application completely.

Reopen the slicer.

Expected behavior:
Credentials should persist, allowing automatic login or "Remember me" functionality on subsequent launches.

Actual behavior:
Login prompt appears every time, requiring full re-authentication.

---

System information:

OS: CachyOS (Arch Linux-based)

Version: Snapmaker Orca Slicer 2.2.1

Installation methods tested: Flatpak and AppImage

Desktop environment: [KDE, GNOME]

[zoncky]

Same here on Fedora Workstation 43, Bazzite Gnome and Ubuntu (Debian).
Flatpak and Appimage don't save credentials, I have to run printer in LAN mode only.

[EndermanAPM]

Same behavior here with Linux Mint 22.3

[Isoceth]

Investigation: Root Cause Identified

After tracing through the codebase, the issue isn't related to SSL certificates — it's that the Snapmaker login token is never persisted to disk.

What's happening

The Snapmaker login flow (SMUserLogin dialog → https://id.snapmaker.com) captures an auth token from the redirect URL and stores it in an SMUserInfo struct (src/slic3r/GUI/GUI_App.hpp:449-475). This struct is a plain member variable on GUI_App:

struct SMUserInfo {
    std::string m_login_user_name = "";
    std::string m_login_user_token = "";
    std::string m_login_user_icon_url = "";
    bool        m_login = false;
};

It lives entirely in memory. When the application exits, the token, username, and login state are all lost. On the next launch, m_login is default-constructed as false and the user is back to square one.

There is no code anywhere that serialises this struct to AppConfig, a JSON file, or any other persistent storage — and no code that reads a saved token back on startup.

Why it affects Linux specifically

The home page "Login or Register" button triggers sm_request_login() (GUI_App.cpp:3837-3839), which uses the Snapmaker-specific login flow. This flow bypasses the inherited Bambu NetworkAgent library (which does have its own token persistence via the closed-source BambuNetworking library). On macOS/Windows, the WebView backend may retain session cookies more aggressively, partially masking the problem. On Linux (GTK WebKit), cookies don't persist between sessions either, so the missing persistence is fully exposed.

Key code locations

File	Line(s)	What
src/slic3r/GUI/GUI_App.hpp	449–475, 738	SMUserInfo struct definition and member variable — memory-only, no persistence
src/slic3r/GUI/WebSMUserLoginDialog.cpp	159–211	Token captured from URL redirect, stored only in memory
src/slic3r/GUI/GUI_App.cpp	3629–3649	sm_get_login_info() reads from the in-memory struct; no disk fallback
src/slic3r/GUI/GUI_App.cpp	3653–3661	sm_request_login() — entry point from the home page login button

What a fix would need

1. Save the auth token and user info to AppConfig or a file in data_dir() on successful login
2. Load the saved token on startup and populate m_login_userinfo
3. Validate the saved token on startup (e.g. call https://account.snapmaker.com/api/common/accounts/current) to handle expiry gracefully

[leavion]

The problem still exists with V2.2.3.