Assigned
Status Update
Comments
me...@gmail.com <me...@gmail.com>
me...@gmail.com <me...@gmail.com> #2
Hi,
Thank you for taking the time to improve libphonenumber!
We are looking into this and will respond as soon as possible.
so...@google.com <so...@google.com>
so...@google.com <so...@google.com> #3
Hi,
Thanks much for raising this issue. This is one of our known issue, which is not documented. Having phone numbers of this long are very rare. libphonenumber cannot do anything better here.
Reasons:
- JavaScript
Number
type has limitation of 2^53 (9007199254740992) as the max literal it can hold. When provided more than that like "90018408059449376"(17 digit), JS starts rounding the value. Unfortunately this is within the range of i.e 17 digit.possible phone number length - Both the alternatives leads to backward-incompatible changes as the type of the field '''national_number''' has to be changed; thus leading to client-side compile issue . Eg: setNationalNumber(1234) / conversions to payloads like JSON.
- Marking the field as
[jstype = JS_STRING]
- Or using new JS data type
BigInt
.
We will update FAQ at GitHub stating some of these points. Maybe you can compare with Number.MAX_VALUE and avoid such cases. Or post request to a Java/CPP/PY libphonenumber clients, as these langs have much more matured data type systems.
bo...@gmail.com <bo...@gmail.com> #5
+923146233552
as...@gmail.com <as...@gmail.com> #6
Wish there was a way to downvote this issue. The haptics feel way better now, y'all are crazy. I can actually feel some feedback from my phone when I'm typing.
lk...@gmail.com <lk...@gmail.com> #7
Same here
Description
What
User experience
What type of Android issue is this?
Other issue
What steps would let us observe this issue?
What did you expect to happen?
The haptics should be deep and crisp as they've always been
What actually happened?
With the latest beta they got stronger but cheap feeling and definitely less refined than before
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
When
Time and frequency
Time when bug report was triggered: Dec 28, 2024 10:06 PM GMT+01:00
How often has this happened?
Every time
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/husky_beta/husky:15/BP11.241121.010/12780007:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 244738036 (24.47.38 (260408-705893532))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677813533 (131.0.6778.135)
System App (Updated)
Network operator: TIM
SIM operator: I TIM
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit