Firebase App Distribution without a Google account: what testers can skip

Nov 3, 2026 · 9 min read

Firebase App Distribution is free, covers iOS and Android, and fits into most CI pipelines. The step that causes the most support messages is not the upload. It is the tester's first minute: an invitation email, a Google sign in, and on iPhone a configuration profile. People search for "Firebase App Distribution without a Google account" because a client, a QA vendor or a stakeholder got stuck at that sign in.

This guide sets out what a tester can skip, what they cannot, how to get someone without a Gmail address through the flow, and what to do about the account errors testers hit most often. The Firebase facts here come from the official Firebase documentation as read on November 2, 2026, with links to each page.

The short answer

A tester cannot accept a Firebase App Distribution invitation without a Google account. The tester guide says it plainly: "When prompted, sign in with Google and accept the invitation to test the app." What a tester does not need is a Gmail address. Firebase notes that a Google account can be associated with any email address, so a tester can create a Google account on their work address and use that.

Where the Google account is needed

The sign in comes up in more places than the first invitation. This table lists each step and whether Firebase asks for a Google account there.

Step	Google sign in?	Notes from the Firebase docs
Accept the invitation	Yes	Invitations can only be accepted once before becoming invalid.
Install on Android with App Tester	Yes	The App Tester app asks for the same Google account used to accept the invitation.
Install on iPhone from the web clip	Yes	The web clip at appdistribution.firebase.google.com lists the test apps for the signed in account.
See pending invitations without email	Yes	The account email must match the address the invitation was sent to.
In-app new build alerts (optional SDK)	Yes	Testers sign in once in the app to turn alerts on.
In-app feedback (optional Android SDK)	Yes	The SDK prompts the tester to sign in if testing features are not enabled.

Sources: tester setup (iOS), tester setup (Android), troubleshooting and collecting feedback.

What testers can skip

A Gmail address. The troubleshooting page tells developers to "ask the tester to link a non-Gmail email address to the account and use that email to sign in."
The invitation emails, after the first one. Testers can open pending invitations in the web clip on iPhone or in the App Tester app on Android instead of searching their inbox.
The App Tester app on Android, in principle. Firebase marks it "optional, recommended". In practice it is the place testers download builds from, so most testers install it.
The Firebase profile, for Enterprise builds. On iOS, installing the profile is required for Ad Hoc builds and optional for Enterprise signed builds, where it only adds the web clip.
Anything in the app itself. Basic distribution needs no SDK. Testers only meet an in-app sign in if you added the optional SDK for alerts or feedback.

What testers cannot skip

The Google sign in itself, for the reasons in the table above.
Device registration on iPhone for Ad Hoc builds. This is Apple's rule, not Firebase's: a device can only install an Ad Hoc build if its UDID is in the build's provisioning profile. Every tool outside TestFlight has the same step.
Developer Mode on iOS 16 and later for Ad Hoc builds. Firebase documents the "Developer Mode Required" error and the fix in Settings, Privacy and Security.
Allowing installs from unknown sources on Android. The browser or App Tester needs permission to install apps outside Google Play.
The Play Store setting for AAB releases. To install an Android App Bundle release, the tester turns on Internal app sharing in the Play Store app once, by tapping the Play Store version seven times in Settings to reveal the switch.

How to get a tester without Gmail through the flow

Send the tester these steps before the invitation goes out. It saves a round of email.

Create a Google account using your existing email address, not a new Gmail address. Google's help page Sign in to your Google Account with another email address explains how; Firebase links to it from its troubleshooting page.
Follow the three rules Firebase lists for the alternate email: do not use a Gmail address, do not use an address already linked to another Google account, and sign in with the Google account password, not the email provider's password.
Open the invitation email. On iPhone, open it in Safari, which Firebase requires so the profile installs and the device registers.
Sign in with that Google account and accept. Use the same account every time afterwards.
On Android, install App Tester when prompted. On iPhone, install the Firebase profile when asked.

The account errors testers hit most

"Google account doesn't have access to test app"

Access is tied to the Google account the tester used when they first accepted the invitation. Firebase's fix is to sign in again with that account. Testers with a personal and a work account on the same phone hit this often, because the browser picks whichever account is signed in.

The tester accepted with a different address

By default, a tester can accept with any Google account, not just the one the invitation was sent to. Firebase explains that this creates a link: when you add Email A to new builds, the account that accepted as Email B gets access. It also means new release emails go to Email A while the tester looks at Email B. To start clean, delete the tester under View all testers in the Testers and Groups tab, invite again, and ask them to accept with the invited address.

If you want acceptance tied to the invited address, turn on Restrict invitation acceptance to recipient's email in the Testers and Groups tab. It is off by default.

403: "Contact your admin for access"

This one is common with company Google Workspace accounts. Firebase says the account "doesn't have permission to install and test apps" and that access is set by the Workspace administrator. The fix is on the admin side, or the tester signs in with another account that is not restricted. For a tester at a large company, that admin request can take longer than the test.

No invitation email

Firebase lists spam folders, mail filters, unsubscribing, and a tester who never accepted the first invitation, in which case later release emails are not sent. Testers can resubscribe from the "Manage email settings" link in an older email or open the web clip or App Tester directly.

Tips for developers to cut the friction

Write a five line note for testers with the steps above and send it with the invitation.
Ask testers which Google account they will use before you invite them, and invite that address.
Use groups so a tester accepts once and gets later releases without a new invitation.
For clients on Microsoft 365, ask early whether they can create a Google account on their work address. Some company policies do not allow it.
Remember invitations expire after 30 days if not accepted. Resend from the tester row before the tester gives up.

When a link without any account is the better fit

If your testers are already on Google Workspace and onboarded, none of this matters and Firebase is a fine choice. It is free, and its 2 GB file limit is generous. The account step matters when testers are outside your company: a client signing off a build, a QA vendor, a beta user who reported a bug.

AppForShare takes the account out of the tester side. You upload an .ipa or .apk, and testers open an install link or scan a QR code on the phone. Nothing else is needed on Android beyond allowing the install. Concretely:

Install from a link, no tester account. Every plan. Free links are password protected if you like and last 7 days; Pro and Team links stay live while subscribed.
Private projects with invited testers (Team). Testers prove their email by opening an emailed link. There is no password and no Google account.
Join links (Team). A tester opens /join/<token>, enters an email, confirms it from their inbox and lands in the project or a tester group. You can limit it to email domains, cap the number of joins and pause it. See tester join links.
Feedback without sign in, on iOS and Android, from the install page or from inside the app with the in-app feedback link. Both are free; screen recordings are Pro.
A tester app without a store (Team). The tester app lists builds shared with the tester and can push new build notices, with no sign in.

What does not change: iPhones still need their UDID in an Ad Hoc profile, and AppForShare has no in-app SDK. Firebase also has things AppForShare does not, such as Crashlytics stability data per build and the App Testing agent. The AppForShare vs Firebase App Distribution page lists both sides, and pricing has the plan limits.

Common questions

Can a tester use Firebase App Distribution with a Microsoft or Yahoo email?

Yes, once they create a Google account on that address. The address itself is fine; the Google account is what Firebase needs.

Can a tester accept an invitation without signing in?

No. Accepting requires a Google sign in, and the same account is then used for installs, alerts and feedback.

Why does the tester see no builds after accepting?

Usually because they signed in to the web clip or App Tester with a different Google account from the one that accepted. Ask which account they used and sign in with that one.

Is there a way to share one build with someone who will never make a Google account?

Not through Firebase App Distribution. You would send the file another way, or use an install link service. On AppForShare a free account gives you a link that works on the tester's phone with no account on their side.