-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert Android Auto support #3397
Conversation
The App v17.1.2 was released without Android Auto support. For now this was the only way Google accepts it. These are the informations that google provides when declining the app with Android Auto support (No idea how "We could not access the in-app content with the login credentials that you have provided." is related to Android Auto...): App Status: Rejected Issue found: Login Credentials In order for us to review your app for compliance with Developer Program policies we will need you to provide valid login credentials for your app, and any other resources needed to review your app. Please note the following requirements when providing login credentials:
In this case:
Additionally, follow these steps to bring your app into compliance: Please consider following these steps to provide instructions for app access Read the instructions in this Play Console Help Center article. Note: The fastest way to resolve this issue and get your app back on Google Play is follow the instructions provided above. If you have already updated valid credentials following the instructions, you do not need to contact our policy support team to provide this information. If you are unable to provide test credentials and instructions or feel our decision may have been in error, please reach out to our policy support team. |
17.1.1 was skipped as it's not released on gplay, for reason see #3397 Signed-off-by: Marcel Hibbe <[email protected]>
This PR reverts #3225 The reason for this is that somehow Google playstore doesn't accept the app anymore when Android Auto support is enabled. There were multiple emails exchanged with google, but there is no reason given that makes sense why the app is declined. Some vague hint was that is is related to Android Auto, and indeed removing Android Auto support finally solved that the app was accepted again. One reason from Google was "We could not access the in-app content with the login credentials that you have provided". But the credentials are provided and working. So it doesn't make sense why/how this is related to Android Auto. For now i give up to understand what's going wrong with the google playstore policy checks. Further hint might be at https://developer.android.com/docs/quality-guidelines/car-app-quality. Signed-off-by: Marcel Hibbe <[email protected]>
7f49e5d
to
d35c91c
Compare
APK file: https://www.kaminsky.me/nc-dev/android-artifacts/3397-talk.apk |
This PR reverts #3225
The reason for this is that somehow Google playstore doesn't accept the app anymore when Android Auto support is enabled. There were multiple emails exchanged with google, but there is no reason given that makes sense why the app is declined. Some vague hint was that is is related to Android Auto, and indeed removing Android Auto support finally solved that the app was accepted again.
One reason from Google was "We could not access the in-app content with the login credentials that you have provided". But the credentials are provided and working. So it doesn't make sense why/how this is related to Android Auto.
For now i give up to understand what's going wrong with the google playstore policy checks.
Further hints might be at https://developer.android.com/docs/quality-guidelines/car-app-quality.
🏁 Checklist
/backport to stable-xx.x