This page provides troubleshooting help and answers to frequently asked questions about distributing and testing apps with App Distribution.
Use the following tips to troubleshoot issues that you might encounter when distributing apps to your testers.
Unable to distribute an app due to a missing contact email
When uploading an app, you might encounter this error:
"We could not find a contact email for app
<app-id>. Please visit
App Distribution within the Firebase console to set one up."
Set a Contact Email in the Firebase console, if available. If the issue persists, contact Firebase Support.
There was an error provisioning your app (400, 409, or 500 errors )
If you repeatedly encounter errors 400, 409, or 500 during provisioning, contact Firebase Support. Provide Support with your Firebase project number and app identifier.
Unable to upload the IPA
The following is an example of a browser network response:
"message": "There was an error processing your
distribution. Ensure you are uploading a valid IPA or APK and try again."
To resolve this issue, follow these steps:
Verify the size of the IPA. The maximum file size limit for all binaries is 2048 MiB, which is a little over 2 GB.
If the IPA size is within the file size limit and is reproducible, follow these steps:
Info.plistfile and confirm whether
<array>delimiters and rebuild your app. The upload should succeed.
If you are still experiencing issues, contact Firebase Support.
If the IPA size is over the file size limit, make any necessary changes to decrease the file size.
Installing and testing apps
Use the following tips to troubleshoot issues that your testers might encounter when they install and test your apps.
Tester doesn't have a Google account
When a user creates a Google account, they automatically receive a Gmail address.
If a tester doesn't have a Google Workspace or Gmail address, or if they would rather use another email address to sign in, ask the tester to link a non-Gmail email address to the account and use that email to sign in.
When choosing an alternate email, the tester must follow these guidelines:
- Don't use a Gmail address.
- Don't use an email address that's already linked to another Google account.
- Remember to use your Google Account password when signing in with this email address.
For more information, see Sign in to your Google Account with another email address.
Tester unable to see the right apps or builds
If the tester accepted the email invitation with a different email address than the invite was sent to, the tester might not be able to see the right apps or builds.
The email that the developer sends invitations to and adds to new builds (Email A) can be different from the email that the tester uses to accept the invitation (Email B). This creates a link behind the scenes. Whenever Email A is added to new builds, it's actually Email B that's getting access.
If the tester accepted the email invitation with a different email address, follow these steps to resolve the issue:
Delete the tester from the View all testers section of the Testers & Groups tab in the App Distribution page of the Firebase console. Existing invitations are removed.
Re-invite the tester to test your app. The tester should receive an invitation email.
Make sure that the tester accepts the invitation with the same email address.
Tester isn't receiving email notifications
Testers might not receive email notifications if one of the following occurs:
Email notifications are sent to spam folders.
Email filters are set.
The invite was sent to one email account, but the tester accepted with a different email account. The tester receives new release emails for the email account to which the invitation was originally sent.
The tester was previously invited but did not accept the initial invitation. If the tester is added to subsequent releases, App Distribution won't automatically send release notifications to that tester because the tester didn't accept the initial invitation.
Ask the tester to check their spam folder and any email filters they set in their email service.
If the tester unsubscribed from the emails, ask the tester to do the following:
- Find an email that the tester previously received from the app.
- Click Manage email settings at the bottom and click Allow emails to resubscribe.
If the tester doesn't care about getting email notifications and just wants to be able to accept app invitations, they can view pending app invitations directly in the Firebase App Distribution web clip: appdistribution.firebase.google.com.
Delete the tester from the View all testers section of the Testers & Groups tab in the App Distribution page in the Firebase console. This action removes existing invitations.
Re-invite the tester to test your app. The tester should receive an invitation email. Make sure that the tester accepts the invitation with the same email address that the invitation was sent to.
"Untrusted Enterprise Developer" error when trying to run test app
The Untrusted Enterprise Developer error appears if you did not trust the developer certificate on the test device before opening the app. In the Settings app > Profiles & Device Management screen, select the app's developer name and trust it.
"Developer Mode Required" error when trying to run test app
The Developer Mode Required error appears when you try to launch an ad hoc-provisioned iOS app on iOS 16 or later without first enabling Developer Mode.
To enable Developer Mode and resolve this error, follow these steps:
- On your iPhone, open the Settings app and then tap Privacy & Security.
- Scroll down to Security and tap Developer Mode.
- Tap the Developer Mode slider.
- Tap Restart.
- After the device restarts, unlock the device. The Turn on Developer Mode? dialog appears.
- Tap Turn On. You can now launch your app and start testing.
"Device registered, you're all set! You’ll get an email when the app is ready to test"
If you're installing an Ad Hoc distribution, this message appears when the developer hasn't yet configured their app to run on your test device. To make the app available to you, the developer must complete the instructions in Register additional devices.
Google account doesn't have access to test app
If your Google account does not have access to a test app you previously installed (or accepted an invitation for), it's likely that you signed in to the wrong Google account. The apps to which you have access are associated with the Google account you used when you first accepted the invitation to test the app. Try again by signing in with the Google account you previously used to accept the invitation.
403 error: "Contact your admin for access"
When you encounter a 403 error, this means that the account you're using doesn't have permission to install and test apps. Access is determined by the administrator of your account's domain in Google Workspace.
If you believe you should have permission to install and test apps, ask your Google Workspace account admin to change your account settings. Your admin should follow the instructions in Manage access to services that aren't controlled individually.
If you have multiple accounts, try logging in with a different account that is not restricted from installing and testing apps.
Enabling in-app alerts with the App Distribution iOS SDK
Use the following tips to troubleshoot issues that involve enabling in-app new build alerts using the App Distribution iOS SDK.
Tester isn't receiving in-app alerts
If you have already set up the App Distribution iOS SDK in your app and your testers aren't receiving in-app alerts, check to make sure your app is fetching new releases:
Enable debug mode in your app. To learn how, see the Google Analytics documentation.
Run your app in a simulator and search for the string "[Firebase/AppDistribution]".
Check that the tester has access to the new release:
If a valid release object is returned, it's likely that there's an issue in the View Controller lifecycle where the alert dialog is loaded before the View appears.
If no release is returned, your tester may not yet be associated with the new release. In the App Distribution dashboard of the Firebase console, make sure your tester is included in your build distribution and is in the Accepted state.
If your tester still isn't receiving updates, ask them to follow the tips below to make sure they accepted the invitation to test your app and that they set up their testing device properly:
On the test device, sign into the Firebase App Distribution web clip. Remember to select the Google account you first used when you accepted the invitation to test the app.
Make sure that the new app release is available in the web clip.
Tester prompted to sign in again after closing app
By default, your testers only need to sign in to their Google account once to enable new build alerts and to install new builds. If your testers are being prompted to sign in again after closing and re-opening your app, follow these tips to make sure your App Distribution configuration is set up properly:
Check to make sure you've enabled the Firebase App Testers API. For more information, see Enable the App Distribution Tester API.
Under Key restrictions, make sure that the Firebase App Testers API is included in the list of allowed APIs.
If you typically clear UserDefaults on signing out, you may be clearing your tester's state. App Distribution stores a flag that indicates whether your tester has already signed into the app. For more information, see the GitHub repository.
Frequently asked questions
Are there limits for adding testers to my app?
Firebase App Distribution has the following tester limits:
Add a maximum of 500 testers to a Firebase project
Add a maximum of 200 testers to an App Distribution group
To add more testers, request a no-cost limit increase.
Do my tester invitations expire?
Testers have 30 days to accept an invitation to test the app before it expires. When an invitation is 5 days from expiring, an expiration notice appears in the Firebase console next to the tester on a release. An invitation can be renewed by resending it via the drop-down menu on the tester row.
When is a new release created for iOS uploads?
How long are app releases available?
App releases are removed from App Distribution if one of the following conditions occurs:
- The app release is older than 150 days.
- You exceed the 1,000 app release limit, and the app release is older than the 1,000 most recent app releases.
For more information, see App Distribution supports a maximum of 1,000 releases.
After the app reaches or exceeds the 150-day expiration limit or the 1,000 app release limit, the release is removed from the App Distribution dashboard and the App Distribution tester web app. If your tester has installed the release, the local version of the app continues to run.
To keep the app release available longer, use one of the following recommendations:
- Before the app release expires or exceeds the release limit, download the IPA and delete the release from the App Distribution dashboard. Then, re-upload the IPA as a new build to App Distribution.
- Download the release and upload it to Cloud Storage for long-term archiving.
App releases expire after 150 days
When you upload a release of your app to Firebase, the release appears in the App Distribution dashboard for 150 days, starting from the upload date. After you upload the release, you can distribute it to testers, who install the release from the App Distribution tester web app on their testing device.
When the release is 30 days from the expiration date, an app release expiration notification appears on your release in the App Distribution page of the Firebase console and in the App Distribution tester web app.
App Distribution supports a maximum of 1,000 releases
App Distribution allows a maximum of 1,000 releases per app. When your app reaches the 1,000 app release limit, App Distribution automatically deletes the oldest releases above the limit.
If you have questions, contact Firebase Support.
What is the Firebase profile?
The Firebase profile is a configuration profile that allows App Distribution to:
Register the test device by collecting the device's unique device ID (UDID). If you're testing an Ad Hoc distribution, Firebase sends the app developer an email that includes the test device's UDID, along with instructions on how to include the device in the app's provisioning profile so that the build can be tested on your device.
Install a Firebase App Distribution web clip to your device's home screen. The web clip allows you to install and access all your test apps in one place. New builds you're invited to test are automatically added to the web clip.
For help on installing configuration profiles on your iOS device, refer to Apple's documentation.
How can I access test apps I installed on my device?
If you're a tester, you can access all of your test apps with the Firebase App Distribution web clip, which is automatically added to your test device's home screen when you install the Firebase profile. If you're testing an Ad Hoc distribution, you must first install the profile before you can test the app.
If you're testing an Enterprise distribution, you can manually install the profile:
If you haven't already, sign in to Google and accept the invitation.
Under Test apps, select the app you want to test.
In the top right of the app's page, tap mobile_screen_share.
Follow the instructions displayed to install the Firebase profile.
How do I delete my tester account?
To delete your App Distribution tester account and its associated data, follow these steps in order:
Visit https://appdistribution.firebase.google.com and sign in with your Google account.
In the top-right, click(Manage account)
Optional: In your Google account permissions, revoke access from Firebase App Distribution. Note that revoking access without first deleting your App Distribution account does not delete your tester account or data.