Problem
Google is refusing to update Vespucci because of an account creation/deletion policy violation https://support.google.com/googleplay/android-developer/answer/10144311?visit_id=638601961422620667-1927855622&rd=1#account_deletion .
While as always google doesn't tell you what the problem actually is, it is likely that the new login screen layout from #4455 triggers this (yes in principle you've always been able to create an account there but now it is much more prominent).
The problem with this is less technical (we could add a button that opens the page with the account deletion button https://www.openstreetmap.org/account/edit), but that if we do this google will hold us liable for the account deletion process by the OSMF which is naturally a non-starter.
Solution proposal
Support an additional parameter to the authorization end point url ( https://www.openstreetmap.org/oauth2/authorize), or a different url that displays a plain vanilla login screen with no other functionality.
It should be noted that there is absolutely no guarantee that this fixes the issue for google and any work done on this could easily be completely in vain.
Problem
Google is refusing to update Vespucci because of an account creation/deletion policy violation https://support.google.com/googleplay/android-developer/answer/10144311?visit_id=638601961422620667-1927855622&rd=1#account_deletion .
While as always google doesn't tell you what the problem actually is, it is likely that the new login screen layout from #4455 triggers this (yes in principle you've always been able to create an account there but now it is much more prominent).
The problem with this is less technical (we could add a button that opens the page with the account deletion button https://www.openstreetmap.org/account/edit), but that if we do this google will hold us liable for the account deletion process by the OSMF which is naturally a non-starter.
Solution proposal
Support an additional parameter to the authorization end point url ( https://www.openstreetmap.org/oauth2/authorize), or a different url that displays a plain vanilla login screen with no other functionality.
It should be noted that there is absolutely no guarantee that this fixes the issue for google and any work done on this could easily be completely in vain.