You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
macOS desktop (0.9.0) does not restore session on launch — credentials persisted but not read #934
Description
After signing in and quitting the app (⌘Q), the app requires a full re-login on
next launch, including re-entering the server address.
Root cause (verified locally)
Credentials ARE persisted to disk but are never read back on startup. In
~/Library/Application Support/com.gooseberrydevelopment.pinepods/credentials/
three files are written correctly at login:
userState.json
After ⌘Q and relaunch these files remain present and unchanged (verified via
ls -la: identical size and mtime), yet the login screen reappears. So the
saved session state is written but not loaded on startup.
Steps to reproduce
Launch app, sign in to a self-hosted server.
Quit with ⌘Q.
Relaunch → login screen, server address empty.
Inspect credentials/ folder → files still present with valid data.
Expected: Session is restored from userAuthState.json on launch. Actual: Persisted credentials are ignored; re-login required every time.
Secondary bug (likely a serialization issue)
serverState.json contains a stray newline in the proxy config:
"proxy_host":"\n"
producing a malformed proxy_url:
"proxy_url":"://\n:/mover/?url="
The trailing "\n" looks like unstripped command output (hostname/container ID)
written into the config.
Fixed in #1039 - It was looking for the login in the wrong place. So should be fixed. Logging out also properly clears it now. Will be released officially with the next release coming soon.
Activity
madeofpendletonwool commentedon Oct 29, 2026
Fixed in #1039 - It was looking for the login in the wrong place. So should be fixed. Logging out also properly clears it now. Will be released officially with the next release coming soon.