search

trunks-social / trunks-public

Issue tracker project
44 stars 3 forks source link

Android app: login using Firefox as external browser fails #165

Open neffscape opened 1 year ago

neffscape commented 1 year ago

If I try to log in using Firefox as an external browser, the process fails.

Using the latest stable version of Firefox (113.0.2), the process fails after filling out and submitting the login form. The cause of the problem seems to be Firefox’s “total cookie protection” feature. Disabling this feature in Firefox allows the process to proceed to the screen where authorization is requested. Clicking on the blue "Authorize" button, Firefox asks if I want to proceed, loading the content of an external application. Selecting the “Open” option, Trunks loads a gray static screen and freezes.

Note: If I repeat the process after already configuring an account (i.e., to add a second account to Trunks), after selecting the blue button on the authorization screen and answering “Open” to Firefox’s request to use an external application to confirm login, Trunks reacts by inserting the URL as text in a new toot. In short, it seems that Trunks does not correctly interpret the authorization returned by the external browser.

Steps to reproduce the error:

  1. Choose Firefox as default browser (Android)
  2. Open Trunks App
  3. Insert your server (in my case: fosstodon.org) and check the “Use external browser to login?” option
  4. Click on the Login button
  5. Insert your login credentials
  6. Login fails because of the “total cookie protection feature”
  7. Disable “total cookie protection” in Firefox and repeat the login process
  8. On the authorization page, select the blue “authorize” button
  9. Select “Open” when Firefox asks to “Leave Firefox to view this content”
  10. Trunks opens, displaying a blank, gray, static screen. The authentication process stops."

Trunks Version: 1.2.1:113 Android Version: Android 10 (EMUI 12.0.0) Firefox Version: (113.0.2)

Decad3nce commented 1 year ago

Firefox has been a constant issue throughout development. I actually never wanted to add an in app browser login but their mobile browser does not behave as an app developer expects. See discussion in #5

I'm not super keen on spending time fixing issues with their browser.