AWS Device farm - Google maps fail to load in app

The issue you're experiencing with Google Maps failing to load in your app on AWS Device Farm is likely due to the app re-signing process that Device Farm performs.

When you upload your app to Device Farm, it re-signs both Android and iOS apps as part of its testing process. This re-signing can break functionality that depends on the app's original signature, and the Google Maps API for Android is one such feature that relies on the app's signature.

The re-signing process essentially changes the app's signature, which can cause the Google Maps API to fail to recognize the app as authorized to use the API. This is because the Google Maps API typically verifies the app's signature to ensure it matches the one associated with the API key you've set up in your Google Developer Console.

Unfortunately, this is a limitation of how Device Farm operates and how the Google Maps API verifies app authenticity. There isn't a straightforward way to bypass this issue within Device Farm itself.

To work around this problem, you might consider:

1. Testing the Google Maps functionality separately from Device Farm, perhaps using emulators or physical devices where you can use the originally signed app.

2. If possible, mocking the Google Maps API calls in your test builds specifically for Device Farm testing. This would allow you to test other aspects of your app without relying on the actual Google Maps integration.

3. Using alternative mapping solutions that don't rely on signature verification for your Device Farm tests.

It's important to note that this issue isn't unique to Google Maps - any functionality that depends on your app's original signature may be affected by Device Farm's re-signing process.
Sources
Sessions in AWS Device Farm - AWS Device Farm
Apps in AWS Device Farm - AWS Device Farm