-
-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser-based login does not work #4592
Comments
Hi, have you also tried the "Login with Browser" item from the three-dots menu on the login screen? |
Yes, that's what I meant with "Browser-based OAuth". |
Ok, but then it does work with the default embedded webview? |
In fact, testing with the most recent version of Tusky available in F-Droid (26.0), I cannot even log in to mastodon.social using the browser based flow, as the issue I mentioned isn't caused by any API call. |
just tried m.s. with tusky 26 from f-droid and it works. probably the only difference between your setup and mine is WebView |
oh sorry you meant browser-flow, missed that |
Could this be the problem? |
Having same issue with browser-based login. Same error as per @charlag above. Android 10, version 26.0 of Tusky app. |
Same problem here, pixel 8, latest os, tusky 26.1, can’t login to chaos.social. |
Any chance this is going to be released in the Google play store soon? At least in the beta channel? I can't use Tusky until that happens (Edit: OMG thank you!) |
Detailed description
When I return from browser-based OAuth, the
domain
,clientId
, andclientSecret
variables are all blank (never persisted to storage), and authentication fails with "An unidentified authorization error occurred.".Steps to reproduce the problem
No response
Debug information
Tusky Test 26.0-0f3dd64c
Google Pixel 6
Android version: 14
SDK version: 34
The account is on my own server software, which implements the right API contract for returning an OAuth code to Tusky (verified with a debugger).
The text was updated successfully, but these errors were encountered: