Install, update and remove the app on Android
Bouncer has no public Play listing or public download. These steps cover the APKs from the private release, which you install yourself (sideloading). Get Bouncer says where the files are and who can get them, and Platforms and status has the state of Google Play internal testing.
What you need
- A phone running Android 9 or later.
- A screen lock (PIN, pattern or password). Bouncer's approval key only works while the phone is unlocked, so Android needs a lock to protect it.
- From the release: the APK,
bouncer-android-<version>.apk, andSHA256SUMS.SHA256SUMShas a checksum for every file in the release: a 64-character string of letters and numbers that only that exact file produces.
Install
-
Check the file, if you can, before installing it. On a computer, in the folder with the APK and
SHA256SUMS:sha256sum -c SHA256SUMS --ignore-missingIt should say
bouncer-android-<version>.apk: OK. On a Mac, runshasum -a 256 bouncer-android-<version>.apkinstead. On Windows, runGet-FileHash .\bouncer-android-<version>.apkin PowerShell. On a Mac or Windows, check that the long string it prints matches the APK's line inSHA256SUMS. If it doesn't match, don't install it, and tell whoever gave it to you. -
Copy the APK to the phone, or download it there.
-
Open the APK on the phone, from your Downloads or Files app.
-
If Android says that for your security it isn't allowed to install unknown apps from this source, tap Settings, turn on Allow from this source, and go back. This permission is for the app you opened the APK with (for example Files or your browser), not for Bouncer. You can turn it off again after installing.
-
Tap Install. Google Play Protect may warn that it doesn't recognise the app, because it didn't come from Play. If you're sure the file came from your organisation, choose to install anyway.
-
Open Bouncer. You should see "Approve access to your secrets from this phone." and the steps To pair this phone.
Next: pair the app with your server.
Update
Install the newer APK the same way, over the one you have. Android keeps your pairing, and you don't need to pair again.
Android only accepts an update signed by the same key as the installed app. If it says App not installed or that the package conflicts with an existing one, the new file was signed differently (for example, a copy from the Play internal track, or a differently signed test build). Don't uninstall to get round it without reading Remove first: uninstalling removes the pairing, and you'll need a new pairing code.
To see which version you have, open Settings (the gear at the top right)
and look under About. It shows the version with its build number, for
example Bouncer 0.5.7+34 (pre-release).
Test builds
Testers may be given an internal test build,
bouncer-android-<version>-internal.apk, through Firebase App Distribution,
Google's service for test builds. At the moment the 0.5.7 internal build is
only for S6 Studios' own testing, and there's no public link
(Platforms and status).
An internal build installs over a build signed with the same key and keeps the pairing. It can't update a copy from Google Play, which is signed with a different key. It shows a red banner, "Internal test build: screenshots allowed", on every screen, and it lets you take screenshots of screens that show a secret. Use it only with test data, and delete screenshots you don't need.
Remove
- In Bouncer, open Settings and tap Sign out. Read the message and tap Sign out again. Bouncer asks your server to revoke this phone, then deletes the pairing and the approval key from the phone.
- Uninstall Bouncer: press and hold its icon, tap App info, then Uninstall.
Uninstalling deletes everything Bouncer kept on the phone. But if you
uninstall without signing out, your server still lists the phone as
paired. Ask your administrator to revoke it. They can find it with
bouncer-admin device list and remove it with bouncer-admin device revoke.
If you reinstall later, Bouncer starts unpaired. When you pair it again, it lists your other devices on this platform under Paired this phone before?, with the command to revoke the old pairing on the server.
If something goes wrong
| What you see | What to do |
|---|---|
| Android won't open the APK | Check the file finished downloading, and that the checksum matches. |
| App not installed when updating | The new APK was signed with a different key. See Update. |
| Bouncer opens on the pairing screen after an update | The old app was removed before the new one was installed, so the pairing was lost. Pair again, and ask your administrator to revoke the old pairing. |
| No notifications | See Troubleshooting. |