chinwag-android/app
Nik Clayton 34de33220c
Don't overwrite the active account when composing from a notification (#3688)
Fix a bug where the active account can be overwritten.

1. Have two accounts logged in to Tusky, A and B
2. Open Tusky as account A
3. Send a DM to account B (doesn't have to be a DM, just anything that creates a notification for account B)
4. Restart Tusky so the Android notification for the DM is displayed immediately. You are still acting as account A.
5. Drag down the Android notification, you should see two options, "Quick reply" and "Compose"
6. Tap "Compose"
7. ComposeActivity will start. You are now acting as account B. Compose and send a reply
8. You'll be returned to the "Home" tab.

The UI will show you are still account A (i.e., it's account A's avatar at the top of the screen, if you have the "Show username in toolbars" option turned on it will be account A's username in the toolbar).

But you are now seeing the home timeline for account B.

Fix this.

ComposeViewModel
- Do not rely on the active account in sendStatus(), receive the account ID as a parameter

ComposeActivity
- Use either the account ID from the intent, or the current active account. **Do not** change the active account
- Pass the account ID to use in the sendStatus() call
2023-05-29 13:32:56 +02:00
..
schemas/com.keylesspalace.tusky.db.AppDatabase Save the a copy of the notification marker ID locally (#3672) 2023-05-18 23:23:42 +02:00
src Don't overwrite the active account when composing from a notification (#3688) 2023-05-29 13:32:56 +02:00
build.gradle Prepare 22.0 beta 6 (versionCode 108) (#3687) 2023-05-24 22:05:25 +02:00
getGitSha.gradle Previous attempt to fix git sha on non-git build broke git build. (#3322) 2023-02-16 20:20:52 +01:00
lint-baseline.xml Ignore LogConditional issues (#3615) 2023-05-04 14:50:21 +02:00
lint.xml Ignore LogConditional issues (#3615) 2023-05-04 14:50:21 +02:00
proguard-rules.pro Remove shrinker rules for okhttp (#3560) 2023-04-24 12:08:03 +02:00