CODEWITHSUNDEEP
androidgoogle-playandroid-auto
Tad
Tad

Reputation: 4784

Problems with Android Auto App Verification

I have noticed that, when I do a staged rollout of an app with Android-Auto support, the app gets re-evaluated every time I change the percentage of users the app is made available to. The evaluation is also tremendously inconsistent, with the app passing about 80% of the time, and failing, with meaningless messages such as "Your app does not perform all functions properly or as expected from a user perspective." If this is not the final, 100% roll out, there is no problem, as the review will likely be different on the next iteration. However, if the rejection happens on the final roll-out, it blocks the app for all users (not just the < 1% that use Android Auto.)

This is largely a rant about Google's flawed evaluation mechanism, but I would like to know if anyone has a way to get the APK evaluated once, so that you can complete the rollout based on a final review, or a way to trigger a new review - changing the config in some trivial way and hitting submit again? Any ways to work through this flawed process would be helpful. Thanks!

Upvotes: 1

Views: 232

Answers (1)

Tad
Tad

Reputation: 4784

It has become clear to us that the Android Auto approval process is too arbitrary and opaque for us to include it in an ordinary release cycle. The best solution was to remove Android Auto support from our application - we could not allow unpredictable failed reviews to disrupt our release cycle, and the reviews did not provide any useful feedback for remedying any app deficiencies - indeed, they seemed to have little to do with our application at all. If Android Auto becomes a significant marketplace presence in the future, we may explore releasing a separate application for Android Auto alone. For now, it seems as though it is not worth the harm caused to other users by interrupting our release cycle.

Upvotes: 2

Related Questions