Skip to content

Troubleshooting

yybam edited this page Oct 7, 2026 · 1 revision

Troubleshooting

Install

"App not installed" / "conflicts with an existing package" An older build with a different signing key is installed. Uninstall it, then install the new one. All v0.3.1+ builds share one key and update in place. See Releases and Signing.

Google Play Protect blocks the install Tap More details → Install anyway (expected for apps distributed outside the Play Store, signed with a new key).

Can't uninstall CORE MDM It's the device admin/owner. Turn off mdmUninstallProtected, disable it in Settings → Security → Device admin apps, then uninstall — or, for Device Owner, remove it from inside the app / factory reset. See Device Owner Setup.

Sign-in

Google Sign-In: "no credentials available" Usually (a) no Google account on the device, (b) no internet, or (c) a captive portal / VPN blocking Google's auth servers. Add a Google account or use email/password. On in-flight or hotel Wi-Fi, finish the portal sign-in first; if an accountability/filter VPN is stale after a network change, reboot to let it reconnect.

Google Sign-In fails on a self-built APK Only APKs signed with the key whose SHA-1/SHA-256 are registered in Firebase can use Google Sign-In. Local debug-keystore builds can't — use email/password, or add your debug SHA to Firebase. See Releases and Signing.

Device Owner

set-device-owner fails: "there are already some accounts" Remove every account (Settings → Passwords & accounts). Some system apps (e.g. Google Meet) re-register — unregister inside the app, or factory reset. A work profile or second user also blocks it.

On a daily-driver phone it just won't take Expected — Device Owner needs an account-free device. Use an emulator to see those features without wiping your phone: Testing with an Emulator.

Console ↔ device

A toggle or command shows "Missing or insufficient permissions" The live Firestore rules are stale. Re-publish firestore.rules (console → Firestore → Rules → Publish, or firebase deploy --only firestore:rules). See Security Rules.

I press Lock but nothing happens on the phone

  • Is the device online (seen in the last 5 min)? If offline, the command waits in the queue until it reconnects.
  • Is the installed build v0.4.0+? Older builds don't read the command queue.
  • Check the queue — the command may be pending; cancel/retry.

Installed Apps tab is empty The inventory uploads when the service (re)starts. Reboot or reopen the app, then reopen the tab. Needs the device online.

Content filter won't start Needs Device Owner (v0.4.1 auto-authorizes the VPN there). On non-Device-Owner devices, Android requires a manual VPN-consent tap the console can't trigger. See Content Filter and DNS.

App-hide / social-media block / enforced PIN do nothing Those need Device Owner. In Device Admin mode they're silently skipped.

Builds / CI

deploy-firestore.yml fails with PERMISSION_DENIED The CI service account lacks the Firebase Rules Admin role. Grant it (see CI-CD and Deployment) or publish rules manually. The workflow is continue-on-error, so it won't block.

APK build didn't run after I pushed build-apk.yml only runs on a tag push (vX.Y.Z) or manual dispatch, not on a normal commit.

Getting logs

adb logcat -v time MdmCommandService:* DeviceRegistry:* EnrollmentManager:* AppPolicyManager:* *:S

Look for Enroll (...) OK, Executing queued command: ..., Remote policies applied, VPN tunnel established, or any FAILED / PERMISSION_DENIED.

Clone this wiki locally