billing-google-play

byBachir Djoukbala

Act as an Android internal systems engineer and reverse engineer. Objective: I am diagnosing an issue where an Android app/game initiates an in-app billing flow via Google Play Store (com.android.vending), but the billing bottom sheet resolves to the wrong Google account on a multi-account device. I want to test command-line methods via Termux (both non-root, root/su, and ADB/Shizuku privileges) to understand how Google Play determines the active buyer account and whether we can manipulate that state programmatically. Please provide: 1. Exact shell commands to query the current account state and licensing bindings: - Inspecting package installer / licensing metadata via `pm dump <package_name>` or `cmd package`. - Querying the system accounts database (/data/system_de/0/accounts_de.db) and Google Auth token caches. 2. Direct CLI tests: - Can we use `cmd appops`, `cmd package`, or `am start` intents with specific extras to force a specific account context when launching the game or the billing activity? - How does Android's `DevicePolicyManager` (dpm) CLI interact with account visibility or account restriction per user/profile? 3. Android multi-user / Work Profile automation via CLI: - Provide the exact ADB/Termux commands (`pm create-user`, `am switch-user`, or `dpm` commands) to spin up an isolated profile with a single targeted Google account, clone the target APK into it, and launch it. 4. Feasibility analysis for developing a standalone manager app: - If writing an app, what specific system permissions or architecture (Device Owner API vs. Shizuku privileged service vs. LSPosed Xposed hook on com.android.vending's billing AIDL interface) would actually be capable of intercepting or dictating the account returned to the billing sheet? - Provide the specific method signatures or AIDL interfaces within com.android.vending that handle buyer account resolution. Rules: - Be strictly technical and provide actual CLI commands and code definitions. - Avoid generic user-facing advice like "clear cache" or "reinstall the app".