Skip to main content
Transform your testing process with: Real Device Features, Company-wide Licences, & App Percy

Setup Google account

This feature will be deprecated on 30 September 2024. Make sure you automate the Google login process and make other necessary code changes before this date. Technical limitations may prevent the feature from working after deprecation.

If you want to test end to end flows with your app, you can also login to a Google account on BrowserStack devices. This can be useful to test scenarios such as :

  1. Test Google in-app purchase flows
  2. Test accepting payments using Google Pay
  3. Test your app’s integration with other Google apps (e.g. Google Calendar)

You can also login to a Google account to test production version of your apps by downloading it from Google Play Store. In order to login to Google account on the device, you need to set the appStoreConfiguration parameter with your Google account credentials in the REST API request to start Espresso tests.

REST API endpoint :

POST /app-automate/espresso/v2/build
Parameter Description Values
appStoreConfiguration Set credentials for Google account login Format: {"username": "play-store-email", "password": "play-store-password"}

Example cURL request :

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST "https://api-cloud.browserstack.com/app-automate/espresso/v2/build" \
-d '{"appStoreConfiguration": {"username": "play-store-email", "password": "play-store-password"}, "devices": ["Samsung Galaxy S8-7.0"], "app": "bs://f7c874f21852ba57957a3fdc33f47514288c4ba4", "testSuite": "bs://e994db8333e32a5863938666c3c3491e778352ff"}' \
-H "Content-Type: application/json"

Parallel tests with the same credentials can trigger Google’s anti-bot security measures. This may lead to additional security checks causing tests to fail. If the Google login feature on App Automate fails intermittently, automate the login flow directly within the test case.

Troubleshooting Google login issues

During test initialization, BrowserStack will attempt to log in on the tested device using specified Google account credentials. In certain cases, Google may pose a 2FA (Two-factor authentication) challenge, which requires you to approve login using a trusted device or an OTP (one-time password) or some other means. This will cause your test build to fail. To fix this, we recommend you to try the following :

  • Use a newly created Google account to sign in. Ensure that this account was never previously used to login on any other device or browser.
  • Turn off the account’s security settings - 2 Step verification and Use your phone to sign in

If you are still facing issues with Google account login, please reach out to BrowserStack support.

Your Google account credentials are secure as we clean the devices at the end of your test session.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Download Copy