Game Center login throws invalid signature after app transfer #14019
Comments
|
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
|
Thanks for reaching out, @orkun1675. The error you encountered looks related to config issue. Make sure that the bundle ID you provided in iTunes Connect matches the bundle ID in your Firebase project. You may also double check your Game Center implementation setup (see our docs for more info). |
|
Thanks for your reply @rizafran Game Center auth requests were working without issue (for the past 1+ years) before the first build we uploaded after the app transfer. Furthermore, our Testflight testers who uninstall the new build and install the old build (that was built using the old Team ID) are able to login again. So I don't think it's a configuration issue. I've tried uploading a build that utilizes iOS Keychain Access Groups. I.e. setting: FirebaseAuth.instance.setSettings(userAccessGroup: '<NEW_TEAM_ID>.com.chunkytofustudios.SharedKeychain');This hasn't worked. Are there any tricks I can use to better debug this? For example, is it possible to set Currently the printed error message ( try {
await firebaseCallWithRetry(
FirebaseService.auth, _auth.signInWithGamesServices);
_log.info('Sucessfully signed into Firebase using Games Services.');
return true;
} on FirebaseAuthGamesServicesException catch (e) {
_log.warning('Failed login due to Games Services error.', e);
} on FirebaseAuthException catch (e) {
_log.warning(
'Failed login due to Firebase Auth error. '
'plugin=${e.plugin} code=${e.code} msg=${e.message} '
'stack=${e.stackTrace} email=${e.email} cred=${e.credential} '
'phone=${e.phoneNumber} tenantId=${e.tenantId} ',
e);
} catch (e) {
_log.warning('Failed login due to unknown error.', e);
}
return false; |
|
Hi @orkun1675, thanks for the repro instructions. Are you able to repro with those instructions? I was wondering if dropping a breakpoint in there could allow for better inspecting the underlying error? Firebase 11.3+ address some issues in the earlier 11.x versions that involved using |
|
Thank you @ncooke3 for looking into this! Please see my questions below. I'm unfortunately am no longer able to reproduce this on my physical iPhone. Downloading old build from App Store and installing the new version via XCode or Testflight does not re-trigger the issue. One hunch we had by looking at logs was the possiblity of iOS version having an impact on the bug reoccurence. However, since iOS emulators cannot access the App Store and physical iPhones cannot downgrade iOS version it is not possible to test this on iOS 17 right now. Furthermore, since we use Flutter we need to wait for firebase_auth to bump internal dependency to I'm going to add more logging to our Testflight builds and ask our beta testers who are still encountering this issue to re-test. I'll report back in a few days. In the meantime, I wanted to double check something with the GameCenter cred signature validation: This block of code obtains both the Note that (1) the
However, (2)
Also note that (3)
Questions
|
|
firebase_auth has upgraded @ncooke3 could you PTAL at this as it's blocking us from releasing updates (including critical privacy fixes) to our app? Maybe the questions I've written above are relevant? |
Description
Users who already had accounts before an iOS App Transfer are unable to login after the app transfer using GameCenterAuthProvider.
Login attempts throw
[firebase_auth/invalid-credential] Invalid signature.Reproducing the issue
Firebase SDK Version
11.2.0
Xcode Version
16.1
Installation Method
CocoaPods
Firebase Product(s)
Authentication
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolvedsnippetReplace this line with the contents of your Package.resolved.If using CocoaPods, the project's Podfile.lock
Expand
Podfile.locksnippetThe text was updated successfully, but these errors were encountered: