Status Update
Comments
pa...@google.com <pa...@google.com>
rb...@google.com <rb...@google.com> #2
I've submitted a fix for this, which should (I hope) make it into Jellyfish Canary 12. There's a relatively straightforward workaround, which is to explicitly declare the version of the com.android.tools.build:gradle
artifact in all build files -- in the screenshot, your project has a versioned classpath
dependency, but also an unversioned one, and it's that unversioned one that tripped up the AGP Upgrade Assistant. Since there is that workaround of making sure that all the classpath dependencies on com.android.tools.build:gradle
have an explicit version, we probably won't patch this for Iguana, I'm afraid.
Thanks very much for the report!
rb...@google.com <rb...@google.com> #3
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Jellyfish | 2023.3.1 Canary 12
- Android Gradle Plugin 8.4.0-alpha12
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
qi...@grabtaxi.com <qi...@grabtaxi.com> #4
rb...@google.com <rb...@google.com> #5
ma...@gmail.com <ma...@gmail.com> #6
same problem in latest koala, AGP upgrade assistant never opens
Please could you open a new issue, and upload enough details about your project to be able to investigate or (ideally) reproduce the problem? Thank you!
im...@gmail.com <im...@gmail.com> #7
su...@gmail.com <su...@gmail.com> #8
sz...@gmail.com <sz...@gmail.com> #9
ro...@gmail.com <ro...@gmail.com> #10
rb...@google.com <rb...@google.com> #11
With that being said, we can see errors have been going down for the last 20 minutes or so.
om...@gnp.com.mx <om...@gnp.com.mx> #12
[Deleted User] <[Deleted User]> #13
rb...@google.com <rb...@google.com> #14
The remaining servers with high error rates and latency appear to be concentrated in Asia, but the situation is improving fast there as well.
ex...@hkmci.com <ex...@hkmci.com> #15
rb...@google.com <rb...@google.com> #16
I'll leave an update when the incident is officially declared to be over.
rb...@google.com <rb...@google.com> #17
[Deleted User] <[Deleted User]> #18
rb...@google.com <rb...@google.com> #19
rb...@google.com <rb...@google.com> #20
rb...@google.com <rb...@google.com> #21
rb...@google.com <rb...@google.com> #22
We consider the incident closed, but keep a close eye on error graphs.
The next steps on Google side will be a thorough review of the incident, with root cause analysis and follow up actions to improve prevention, detection, and mitigation of similar issues in the future. From this detailed analysis, we'll produce an incident report which we'll share with you here. I'll keep this bug open until then.
rb...@google.com <rb...@google.com> #23
Thank you all for your patience so far. If you still experience elevated error rates of latencies, please let us know.
[Deleted User] <[Deleted User]> #24
wi...@gmail.com <wi...@gmail.com> #25
Region: Singapore
rb...@google.com <rb...@google.com>
[Deleted User] <[Deleted User]> #26
Let me know the way to avoid this problem in the future.
Can we have multiple endpoints in different regions and request to healthy region when the some of them fails and finnally get the healthy response?
jh...@google.com <jh...@google.com> #27
va...@gmail.com <va...@gmail.com> #28
Anaheim CA
Costa Mesa CA
Pensacola FL
Fort Worth TX
Kissimmee FL
San Diego CA
Houston TX
Please keep us posted on when this can be fixed.
Description
Most affected APIs:
- Geocoding API;
- Place Search API.
Symptoms:
* The affected APIs saw a sharp increase in 5xx errors rate, starting around 2019-11-13 17:50 PST.
* Elevated latency is also happening on the same APIs.
Our engineering team continues to investigate on the issue.
For those who are affected, we apologize for the disruption.
Please follow this Issuetracker entry by clicking the star icon to receive the latest update on this issue.