I’m experiencing an issue where Messenger in WebCatalog does not persist login sessions. Each time I close and reopen the app, I’m logged out and have to sign in again.
I understand Meta has some security policies that may interfere with non-standard environments. I’ve tested this across different tools:
- Franz also fails to persist sessions.
- However, when I install Messenger as a PWA in Google Chrome, it does persist sessions correctly.
This suggests WebCatalog might be sending something (user-agent, environment metadata, etc.) that causes Meta to distrust the session and not store persistent login tokens.
Additional notes:
- New Messenger sessions in WebCatalog do not persist.
- Older sessions (from before) used to work, but after I closed the last active session on my laptop, those also now log out.
- I found a temporary workaround by creating a custom WebCatalog app using the URL:
https://www.facebook.com/messages/
This version persists sessions properly.
The problem is that using this Facebook-based URL disables notifications.
It appears Meta is treating messenger.com and the normal facebook.com URL differently. I’m hoping there’s something WebCatalog can do to improve compatibility or mimic standard browser behavior more closely to support session persistence and notifications at the same time.
Has anyone found a more permanent solution?