-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Not planned
Labels
blocked: customer-responseWaiting for customer response, e.g. more information was requested.Waiting for customer response, e.g. more information was requested.platform: iosIssues / PRs which are specifically for iOS.Issues / PRs which are specifically for iOS.plugin: authresolution: needs-reproThis issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin.This issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin.type: bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues.To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Which plugins are affected?
Auth
Which platforms are affected?
iOS
Description
A user has reported that the app has crashed several times when returning to it after being authorized with X in the web tab. The unstable network condition could be somehow affected because the user has reported that a VPN is being used during the process.
Reproducing the issue
- Start the authentication flow with the
TwitterAuthProvider
. - Authorized, and returning the app.
- After a few seconds, the app crashes.
The pseudo code I was calling:
Future<void> _startAuth() async {
final provider = TwitterAuthProvider();
provider.setCustomParameters({
'scopes': 'users.read offline.access',
'lang': 'en',
});
final credential = await _$.signInWithProvider(provider);
final idToken = await credential.user?.getIdToken();
if (idToken == null) {
return;
}
// Making HTTP requests with `idToken`.
}
Firebase Core version
3.13.0
Flutter Version
3.27.4
Relevant Log Output
See the attached crash log.
Flutter dependencies
Expand Flutter dependencies
snippet
dependencies:
- firebase_auth 5.5.2
- firebase_core 3.13.0
transitive dependencies:
- firebase_auth_platform_interface 7.6.2
- firebase_core_platform_interface 5.4.0
Additional context and comments
Detailed information can be found in the log file.
Hardware Model: iPhone 14 (iPhone14,7)
OS Version: iPhone OS 16.7 (20H19)
Searched related issues:
- [firebase_auth]: Microsoft Federated identity sign-in not working with Firebase MFA enabled authentication credentials/user in iOS platform #16929
- 🐛 [cloud_firestore] FIRESTORE INTERNAL ASSERTION FAILED #6927
- 🐛 [firebase_core] Firebase crashes on iOS #5856
- 🐛 [firebase_dynamic_links] iOS app crashes when users click on the dynamic link #4882
- FIRESTORE INTERNAL ASSERTION FAILED: QueryComparator needs to have a key ordering. (expected has_key_ordering) firebase-ios-sdk#7672
- Crash: LevelDB not created for Firestore with large data set firebase-ios-sdk#4333
Metadata
Metadata
Assignees
Labels
blocked: customer-responseWaiting for customer response, e.g. more information was requested.Waiting for customer response, e.g. more information was requested.platform: iosIssues / PRs which are specifically for iOS.Issues / PRs which are specifically for iOS.plugin: authresolution: needs-reproThis issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin.This issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin.type: bugSomething isn't workingSomething isn't working
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
MichaelVerdon commentedon May 21, 2025
Hey there, are you able to reliably reproduce this? If so, would you be able to send a full MRE over for further investigation?
AlexV525 commentedon May 22, 2025
Not from my side but the client said it happens 1/10~2/10.
You mean my development environment? macOS 15.3.2, Xcode 16.2, iOS deployment target 15.5.
MichaelVerdon commentedon May 22, 2025
Hi there, I meant a full code example or a repo showing how you implemented it. Do you also know what devices these users were using?
AlexV525 commentedon May 22, 2025
@MichaelVerdon
Sorry, but below (as previously said) was basically all necessary code:
Setup the provider, call authorization, and get the
idToken
.As previously described:
14 remaining items