Status Update
Comments
kk...@google.com <kk...@google.com> #2
Hey, sorry for coming back to this so late. We've never seen this. Without any repro steps it's going to be hard to do anything about it.
We've some cases where the Gradle daemon gets started but Studio cannot connect to it and the Studio side Gradle code handling connection to the daemon will keep spawning new ones if the connection does not get established. In this instance though the fact that the build window shows all these daemon running means that this is a different problem.
li...@vonage.com <li...@vonage.com> #3
Hello, I had the issue reproduce on first project open after upgrading Android Studio from JetBrains Toolbox. Note that the project has a buildSrc.
I think you can reproduce it with the same steps if nothing changed since Arctic Fox alpha 08.
li...@vonage.com <li...@vonage.com> #4
When you upgraded from the toolbox, can you indicate which version you started from and what you upgraded to?
kk...@google.com <kk...@google.com> #5
Yes, actually it's in the title of the issue: Canary 7 to 8 of Arctic Fox.
Description
We noticed the libphonenumber tool returned "Invalid" results for the below Brazil numbers. These numbers are linked with active WhatsApp accounts so they should be valid. Please help check the issue. Thank you.
Country: Brazil
Example number(s) and/or ranges:
+556598007355
+558296140444
+554188819028
+558796239662
+559891371174
+557581880335
Where or whom did you get the number(s) from: my customer
Authoritative evidence (e.g.national numbering plan, operator announcement):
WhatsApp accounts with these numbers are active, which at least means these numbers can receive OTP via SMS or Calls from Meta. They shouldn't be invalid. Please see the screenshots attached.
Link from demo (