1

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!

4

1 回答 1

1

我们很清楚，Android Auto 的审批流程过于武断和不透明，我们无法将其包含在普通的发布周期中。最好的解决方案是从我们的应用程序中删除对 Android Auto 的支持——我们不能让不可预测的失败评论破坏我们的发布周期，并且评论没有提供任何有用的反馈来弥补任何应用程序的缺陷——事实上，他们似乎没什么可做的我们的应用程序。如果 Android Auto 在未来成为重要的市场存在，我们可能会探索单独为 Android Auto 发布一个单独的应用程序。目前看来，中断我们的发布周期对其他用户造成的伤害似乎是不值得的。

于 2015-08-04T20:52:36.233 回答