Adding second Account isn't working

[branleb]

Detailed description

Adding the first Account after Installing the App on Android 15 just worked fine. Adding a second account with another Instance doesn't seem to work anymore.

The following is the same whether Chrome Custom Tabs are enabled in App Settings or not.

If I use the "Login with Tusky" Button Tusky opens the In-App-Browser with login page of said instance (in my case: ohai.social)
After logging in the Browser shows the Homepage with the Timeline. No OAuth-Authorization Request or something alike is shown. (So something seems to be going wrong here)
Hitting the "Back Navigation Item" (Backwards Arrow Top Left Corner) brings me back to the Instance Entering Screen.

If I hit "Open With Browser" via the three-dots-menu, it opens in Browser. Here, the OAuth Authorize Screen with the requested permissions is shown. After hitting "Authorize", it becomes obvious that even though the Browser is shown in the App in the App Overview Screen, that this variation respects the default browser choice (and via the browsers three-dots-menu I can even open the page in the Browser App)

Indenpendent of opening it in the integrated Browser or opening the browser app via the menu, the following happens:

If Firefox is my default Browser, the OAuth Authorize Screen with the requested permissions is shown. After hitting "Authorize" Firefox asks whether I want to leave Firefox to view this content (Title: "Open in another App") with the Options "Cancel" and "Open". The latter one brings me back to the Tusky Apps "Enter Instance"-Screen with an error message "An unidentified authorisation error occurred".

If Chrome is my default browser, the behaviour is one of the following two:
a) If I'm logged in in the current chrome session after some loading time the Tusky Enter Instance Screen is shown with an error message about not beeing able to authorise with the instance.
b) If the current chrome session is not logged in, the login screen of the instance is shown in browser. After logging in i'm redirected to the homepage / Timeline.

So, in Summary: Something really seems to be wrong with chrome, either Chrome itself or the way Tusky calls Chrome. Indepently of Chrome, there seems to be a Bug/Misbehaviour in Communicating with any Browser App as neither the In-App-Browser nor Chrome or Firefox seem to work when trying to add a second account.

Steps to reproduce the problem

1. Install Tusky
2. Setup first Account
3. Go for Adding another Account
4. Enter Instance URL
5. Hit "Login with Tusky" or "Login with Browser"
6. Identify to the Instance
7. See failure (In-App-Browser/Chrome) or
8. Authorize Access
9. Confirm Firefox to open Content in other App
10. See error message
    ...

Debug information

Tusky 26.2
Device: Google Pixel 8a
Android version: 15
SDK version: 35

Chrome 131.0.6778.135
Android 15; Pixel 8a Build/AP4A.241205.013

Firefox: 133.0.3 (Build #2016060959), hg-7ed49fe90e84+
GV: 133.0.3-20241209150345
AS: 133.0

[connyduck]

This is very likely fixed in the current beta #4704

Can you please try it out?

[branleb]

This is very likely fixed in the current beta #4704

Can you please try it out?

Could find an easy way to install the current beta as singning up for the beta programme in google play and even un- and reinstalling the app left me with v. 26.2 (and no change in behaviour)

I tried the nightly build ( https://play.google.com/store/apps/details?id=com.keylesspalace.tusky.test )
Behaviour with In-App-Browser and Chrome is the same as above.

But with Firefox as default Browser, it worked. So at least in some part, that seems to be fixed with the current code.