Firebase-ios-sdk: Firebase Auth Token showing invalid when entered in Firebase ABTesting test device

[samarth220194]

[REQUIRED] Step 1: Describe your environment

• Xcode version: Version 11.6 (11E708)
• Firebase SDK version: 6.27.0
• Firebase Component: RemoteConfig / ABTesting
• Installation method: file

[REQUIRED] Step 2: Describe the problem

• Steps to reproduce:
• Use code snipped to retrieve the Auth Token (see next section)
• Go in firebase console and enter this Instance ID Token in Manage test device for an A/B test.

See the following error:

Relevant Code:

 Installations.installations().authToken(completion: { (token, error) in
        if let error = error {
            print("Error fetching token: \(error)")
            return
        }
        guard let token = token else { return }
        print("Installation auth token: \(token.authToken)")
    })

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[maksymmalyhin]

@samarth220194 Sorry you experience the issue. It looks like a bug on the Firebase Console side that still does validation against the old Firebase Instance ID token format not accepting the new Firebase Installations token. I'll pass the issue to the console team.

In the meanwhile as a workaround you may install FirebaseInstanceID SDK for debug build variant only to get the token in the old format:

• Podfile example
• get token example

[maksymmalyhin]

cc @egilmorez @morganchen12

[maksymmalyhin]

Tracked internally at b/172454592

[samarth220194]

@maksymmalyhin This happens when I edited a running experiment, and post that I tried to add new test devices.
It doesn't happen in a newly created experiment.
I hope this would help in further debugging.

[tgpsantos]

@maksymmalyhin is this happening with Android devices also? I'm getting a similar issue in the Flutter plugin. Tbh this was the first time I tried it so I might be missing something,

[maksymmalyhin]

@maksymmalyhin is this happening with Android devices also? I'm getting a similar issue in the Flutter plugin. Tbh this was the first time I tried it so I might be missing something,

@tgpsantos As this is a console issue, I think yes, it most likely relevant for Android apps as well.

[kivraoskar]

@maksymmalyhin This happens when I edited a running experiment, and post that I tried to add new test devices.
It doesn't happen in a newly created experiment.
I hope this would help in further debugging.

Tried making a completely new experiment but it still did not work for me

[kivraoskar]

@samarth220194 Sorry you experience the issue. It looks like a bug on the Firebase Console side that still does validation against the old Firebase Instance ID token format not accepting the new Firebase Installations token. I'll pass the issue to the console team.

In the meanwhile as a workaround you may install FirebaseInstanceID SDK for debug build variant only to get the token in the old format:

• Podfile example
• get token example

Just tried this out, and it didn't solve the problem for me. Still get invalid token error.

[seviu]

@kivraoskar As I explained in https://github.com/firebase/firebase-ios-sdk/issues/6892#issuecomment-721795650 using the old format works in the firebase console, but to no effect because the device does not get the experiment I set.

[tgpsantos]

@maksymmalyhin is this happening with Android devices also? I'm getting a similar issue in the Flutter plugin. Tbh this was the first time I tried it so I might be missing something,

@tgpsantos As this is a console issue, I think yes, it most likely relevant for Android apps as well.

Thanks! Is there any issue/PR where I can track the fix release? Or ETA?

[paulb777]

@tgpsantos There is active investigation and we'll follow up here when there's something to report.

[maksymmalyhin]

@tgpsantos @samarth220194 Could you please try it again with a fresh Firebase Installations Auth Token? The token has expiration period around 1 week. Currently the expired token may be a reason of validation failure.

[samarth220194]

@maksymmalyhin I am working on some other project for now. Won't be able to help you with this right now. @tgpsantos can you please re-try and help @maksymmalyhin with the update?

[brandtnewww]

I just tested it with the current react-native-firebase package by Invertase (https://github.com/invertase/react-native-firebase) and with the AuthToken, it works. I get the token and on refreshing the device, I get the correct a/b test variant.

[google-oss-bot]

Hey @samarth220194. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[kivraoskar]

@maksymmalyhin I just tried again with the Installations Auth token and it is still not working for me.

Still getting Error saving test devices: Instance ID token is invalid

[sknopf]

@kivraoskar 👋 Firebase dev here. A few quick checks:

• Did you try generating a fresh token and re-registering it with ABT? Installation Auth Tokens expire after 7 days.
• Do you have multiple Firebase projects you're managing? If so, please double check you're registering with the same project your app is configured to.

Validation errors we commonly see often fall into one of those two categories. If those don't apply, let us know and we'd be happy to look into this further.

[google-oss-bot]

Hey @samarth220194. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@samarth220194 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

[kivraoskar]

@sknopf Sorry for slow answer. Been away on holiday vacation last two weeks.

Just checked again and made sure I had the correct project selected and created a fresh ABT token via Installations (same code as mentioned in the first post). I'm unfortunately still getting the same error.