No. Each tool reads the file in your browser. Only the optional "Share this build with testers" button uploads it, as a normal upload.

Why does Firebase need a different SHA-1 for my Play app?

With Play App Signing, Google signs the app users install with its own key. Add the app signing key's SHA-1 from Play Console as well as your upload key's.

Is there a limit on file size?

No limit of ours: the browser reads the file on your computer.

AppForShare Create a free account

Free build tools that never upload your file

Free, no account

Some build questions come up every week: what is inside this .aab, which SHA-1 does Firebase want, which method goes in ExportOptions.plist since Xcode renamed them. Answering them usually means a terminal, a keystore password or an old blog post.

Three free tools answer them in the browser. Your file is read on your computer and is never uploaded, and you need no account.

Start free See plans

Example

APK analyzer, signing certificate

SHA-15E:8F:16:06:2E:A3:CD:2C:4A:0D:54:78:76:BA:A6:F3:8C:AB:F6:25
SHA-256FA:C6:17:45:DC:09:03:78:...
Expires2051-03-14

Read in your browser. Same values as keytool -printcert.

Made for

Android developers adding a key to Firebase or Google Cloud
iOS developers exporting builds from CI with xcodebuild or fastlane
Anyone handed a build file who wants to know what is in it

What it ends

Running keytool and apksigner just to read a fingerprint
Guessing which ExportOptions.plist method name a new Xcode expects
Unzipping an .aab and reading protobuf by hand

How it works

Step 1
Open a tool
AAB inspector, APK analyzer or the ExportOptions.plist generator, from the free tools page.
Step 2
Drop a file or fill the form
The file is read by your browser. The plist is made in your browser too; nothing is sent.
Step 3
Copy what you need
Copy a fingerprint, download the plist with the matching command lines, or share the build with testers through a normal upload.

AAB inspector and APK fingerprints

The AAB inspector reads a bundle's modules (base, feature modules and asset packs with how each is delivered), package, version, minimum and target SDK, device type, launch activity, native ABIs, the bundletool version, permissions in plain words and the upload key with its fingerprints, then runs the Google Play readiness rules on the base module.

The APK analyzer now shows the signing certificate's SHA-1, SHA-256 and MD5 with copy buttons, colon separated and upper case as Firebase, Google Cloud and keytool use them, with the subject and expiry. With Play App Signing, apps installed from Google Play are signed with Google's key: add that SHA-1 from Play Console too.

ExportOptions.plist generator

Pick the method (release-testing, app-store-connect, debugging, enterprise, or the older ad-hoc, app-store and development names), team ID, automatic or manual signing with a profile per bundle ID, App Store Connect options and Swift symbol stripping. Download or copy the plist, with the matching xcodebuild archive and -exportArchive lines and a fastlane gym line.

Good to know

The AAB inspector does not convert an .aab to an APK. Upload the .aab with a free account and AppForShare makes the APK testers install.
The tools read and explain; they do not sign, re-sign or change a file.
Readiness results are guidance, not a promise of store approval.

Questions

Is my file uploaded?: No. Each tool reads the file in your browser. Only the optional "Share this build with testers" button uploads it, as a normal upload.
Why does Firebase need a different SHA-1 for my Play app?: With Play App Signing, Google signs the app users install with its own key. Add the app signing key's SHA-1 from Play Console as well as your upload key's.
Is there a limit on file size?: No limit of ours: the browser reads the file on your computer.