Fixed
Status Update
Comments
ve...@google.com <ve...@google.com> #2
Great, thank you for the update and analysis.
is currently still being investigated, and I will be sure to update the internal report with the informative info you provided. Thank you so much.https://issuetracker.google.com/issues/122098785
ga...@google.com <ga...@google.com>
ga...@google.com <ga...@google.com> #3
I can just second this. This is the far most pressing issue of the Android ecosystem for developers and users and despite the Android's team promise to force OEM into being more transparent about the non-standard restrictions they are doing, nothing is really happening and the situation is worst and worst year a over year (with the only bright exception of Nokia)..
Not only new restrictions are being introduced year by year, but in addition OEMs maintain app whitelists which are highly anti-competitive and even more damaging for smaller developers..
The only education for the users on what is happening now comes from thehttps://dontkillmyapp.com/ project and in most cases it reaches them ex post when they are already angry with their developers.
Not only new restrictions are being introduced year by year, but in addition OEMs maintain app whitelists which are highly anti-competitive and even more damaging for smaller developers..
The only education for the users on what is happening now comes from the
ma...@tgsmc.com <ma...@tgsmc.com> #4
Hello
Description
This will create a public issue which anybody can view and comment on.
Problem you have encountered:
Running
gcloud source repos clone {repo}
adds a local git config of:...and because this isn't restricted to only Google Cloud, it prevents any other remote that also requires a credential helper from working.
What you expected to happen:
Restrict to only Google Cloud, like:
Steps to reproduce: