Edit history

Opening a push notification to a different instance causes broken state has not been edited, so there are no earlier versions.

Current version | Original by probablyjassin
Show

Opening a push notification to a different instance causes broken state

Reproduction steps

  1. I logged into the Android app with my fluxer.app account (btw now automatically assigned fluxer.com in the app)
  2. I also added my account on my self hosted instance
  3. I switched back to my fluxer.app account
  4. I closed the app
  5. Receive and tap on a push notification from my self-hosted instance

Observed behaviour

While the app is loading, you can briefly see the "We fluxed up" screen before getting sent to the correct instance. The previously selected instance (my case: my fluxer.com account) now is listed as "expired", I am seemingly logged out of it. The username is still there, but it's URL is listed as the other (my case: my self-hosted instance) URL, not fluxer.com. Clicking on this account entry fills in my fluxer.com username into the email field of the login screen, also with my self hosted instance selected instead though. Even after restarting the app, this persists. But in the background I'm still logged into the instance with the broken state. I could tell because I still receive push notifications from it. After extensive testing I can also say that this doesn't happen in 100% of cases. Other times, clicking the notification would open Fluxer but then not send me to the other instance at all. In this scenario, the "expired" issue does not happen.

Build information

Version 2026.09.100, Beta 4, Channel Beta, Build 2547, Android 16 (arm64), Device samsung SM-S918B, Locale en-GB, Push fcm, Flutter 3.47.5, Dart 3.13.4

Platform

Android

Details

Expected behaviour The app opens to the instance that the notification came from with no other issues