MaikuB / MaikuB/flutter_appauth
Login button unresponsive on some Android devices with flutter_appauth: ^9.0.1
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 308
- Forks
- 301
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Description
Description
On certain Android devices, the login page loads correctly, but when the user clicks the Login button, nothing happens. The login process does not continue, and no redirect or error is triggered.
This issue only occurs on specific devices. On other devices, the login flow works as expected.
Affected Devices
Redmi A22-Android 11, upgradable to Android 13, MIUI 14
ZTE Blade V50- Android 13 or Android 14
Blackview Wave 8 -DokeOS 4.0 Based on Android 14
Nokia C22 - Android 13 Go Edition
Redmi 9-Android 10 and MIUI 11 or Android 12 with MIUI 13
itel A50 - Android V14.0.1
Vivo-2015 -Funtouch os 10.5, Android vertion 10
Steps to Reproduce
Install the app on one of the affected devices.
Trigger the login flow using flutter_appauth.
The authorization page loads.
Tap the Login button.
Nothing happens – the button is unresponsive.
Expected Behavior
After tapping Login, the app should redirect back with an authorization code/token as it does on working devices.
Actual Behavior
The Login button does not respond. The user cannot continue with the authentication flow.
Environment
Package: flutter_appauth: ^9.0.1
Flutter version: Dart 3.7.2 • DevTools 2.42.3
Android versions: minimum android SDKk Vertion 21
Identity provider: IdentityServer
Additional Notes
Works fine on other devices (e.g., Samsung, Pixel,iphone).
No error messages in logs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. First reproduce the login flow on one of the listed Android devices with flutter_appauth ^9.0.1 and compare it with a working Samsung, Pixel, or iPhone setup; investigate the Android authentication path without assuming a logged error. Done means tapping Login consistently continues the flow and returns the expected authorization code or token on the affected devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100