I'm developing a small personal app with the Android for Cars App Library (a CarAppService with list templates) and want to test it in my car.
Android Auto's "Unknown sources" developer option doesn't apply to Car App Library apps (docs). Google's documented way to test one in a real car is to install it from the Play Console internal test track or Internal App Sharing. The usage guide says apps must be installed from the Play Store to show up in Android Auto. Is an install from a Play testing track expected to work on GrapheneOS?
The reason I'm asking first: Android Auto's app validator never seems to reach the Play Store. With my sideloaded test build, every check logs this, even after force-stopping Play services, the Play Store and Android Auto and opening the Play Store first (package name replaced):
W CAR.VALIDATOR: isPackageInstalledByPlayCheck service not connected
W CAR.VALIDATOR: Package DENIED; failed all other checks [com.example.carapp]
The denial itself is expected for a sideloaded app. But if the Play install check can't connect, I'd guess a Play testing-track install would be denied too, since such an app isn't on Google's list of approved apps the way published ones like OsmAnd are.
Is that check intentionally unavailable because of Android Auto's reduced privileges, or is there a permission under Settings → Apps → Sandboxed Google Play → Android Auto that enables it? I'd rather know before paying for a Play developer account just to test this.
Pixel 10 Pro XL, GrapheneOS 2026100601, Play services 26.32.34 (260400-968093310), Play Store 53.1.27-34 [0] [PR] 979879791, Android Auto 17.6.663454-release, wired Android Auto in the Owner profile.