CODEWITHSUNDEEP
firebasefirebase-remote-configfirebase-test-lab
Bitwise DEVS
Bitwise DEVS

Reputation: 3449

Firebase Services not working with Firebase Test Lab devices due to the APK is being re-sign

I am doing a test with Firebase Test Lab but the emulator cannot continue most likely due to having problem with Firebase SDK. The app cannot continue after the splash screen because it need Remote Config to fetch successfully if failed then AlertDialog is shown.

enter image description here

Error log from Test Lab

enter image description here

enter image description here

enter image description here

I checked the app-debug.apk SHA and it was the same as what is registered in the Firebase project and Cloud console and I can run it locally on my device.

Upvotes: 0

Views: 1040

Answers (2)

Stanislav Negara
Stanislav Negara

Reputation: 662

Your Roboscript fails because the app fails to start properly and thus, Roboscript cannot perform its actions.

If Remote Config fails to fetch due to your app's APK being re-signed, then you can make Robo try to crawl your app without re-signing the APK by making sure that your app stops when Remote Config fails to fetch without any additional dialogs (shown in your crawl graph). In FTL, when Robo detects that an app could not be crawled after being re-signed, it will attempt to crawl it without re-signing.

Upvotes: 1

P. Davis
P. Davis

Reputation: 1007

The likely problem here is that Robo generally must re-sign your app before running your test in FTL.

There's a new feature in the Testing API that let's you set the Robo test mode to ROBO_VERSION_1, which will run Robo in UIAutomator-only mode without resigning the app. Unfortunately that feature is not exposed yet in the Firebase Console or the gcloud CLI.

Upvotes: 1

Related Questions