Google Play 最近的审核通知 - APK 有一个突出的披露但披露不充分
我们最近收到了来自 google play 团队的通知，指出“需要采取行动：您的应用不符合 Google Play 政策”。他们声明要在 7 天内解决更改，否则该应用程序将从 Google Play 商店中删除。请参阅下图中的资格问题。
他们解释说该应用程序正在向https://cloud.codenameone.com发送用户电话号码信息。我们可以认为导致这种情况的唯一原因是可能发送用于调试的崩溃报告日志。应用程序中的任何其他信息只会存储在设备本身上。
谷歌突出披露和同意要求规定：-
您必须在应用内披露您的数据访问、收集、使用和共享。应用内披露：
- 必须在应用程序本身内，而不仅仅是在应用程序描述或网站上；
- 必须在应用程序的正常使用中显示，并且不需要用户导航到菜单或设置；
- 必须描述被访问或收集的数据；
- 必须解释数据将如何使用和/或共享；
- 不能只放在隐私政策或服务条款中；和
- 不能包含在与个人或敏感数据收集无关的其他披露中。
您的应用内披露必须伴随并紧跟在请求用户同意和相关运行时权限（如果可用）之前。在用户同意之前，您不得访问或收集任何个人或敏感数据。应用程序的同意请求：
- 必须清楚明确地呈现同意对话框；
- 必须要求肯定的用户操作（例如，点击接受，勾选复选框）；
- 不得将导航远离披露（包括轻触或按下后退或主页按钮）解释为同意；和
- 不得使用自动关闭或过期消息作为获得用户同意的手段。
Our app currently requires only the phone permission since the app launches to the message app to send programming SMS messages. This is the only permission currently applied. When using the crash report feature for codename one is there some other permission that needs adding in some way? Or does it look like we will need to remove the log feature and resubmit. Any advice on how to resolve this would be greatly appreciated.
It's been weeks but our app is finally live after countless attempts and retries it turned out to be the dumbest thing and most insane example on how the Google review process is broken.
It seems that Google fails a production app even if an old PAUSED test channel exists with an old version of the app. They indicate this in the version of the APK (1.91 in your case which corresponds to 191). I'm guessing that's just a very old version that's nowhere close to the current version you have in production. The solution is to go one by one to the internal, alpha, beta channels and promote a release then finally publish to production.
It's insane that they would suspend the production app because of that. It's insane that they won't say that in the email and throw a misdirect in a completely wrong direction. It's insane that their UI/UX is so awful that I tried to update the APK in these channels a week ago and it seems that this update just didn't go through because I needed to follow through another stage and promote to the next level.
Note: This answer was edited to reflect the correct answer, this is the original answer which might be still valid for some edge cases...
Is it possible this is a very old build?
We had this ourselves for one of our apps. Historically we used the phone access permissions for Codename One apps to work around bugs in older versions of Android (not collect numbers as they incorrectly imply). Simply creating a new build might workaround this problem.
In the case of our app I just sent a new build and uploaded a new version and so far it's still up (2 weeks later) so it seems to be the right thing.
编辑：我还就此写了一篇博客文章：https ://dev.to/codenameone/google-play-kafkaesque-experience-mp3