Fixed
Status Update
No update yet.
Comments
ma...@google.com
Information redacted by Android Beta Feedback.
c....@gmail.com
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ma...@google.com
- Build Number: google/oriole_beta/oriole:UpsideDownCake/UPB1.230309.014/9890577:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Same problem on beta 1. Re-registering fingerprints doesn't help.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561504834 (112.0.5615.48)
System App (Updated)
Network operator: One NZ
SIM operator: vodafone NZ
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Same problem on beta 1. Re-registering fingerprints doesn't help.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561504834 (112.0.5615.48)
System App (Updated)
Network operator: One NZ
SIM operator: vodafone NZ
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ma...@google.com
Information redacted by Android Beta Feedback.
c....@gmail.com
Same issue and it also will not allow me to register new fingerprints. Android 14 Beta 1
ma...@google.com
Android 14 Beta 1 has this same issue. I've even tried removing all fingerprints and readding them with no luck. Rebooting doesn't fix it. You're always forced to enter your PIN or Pattern code. Face Unlock seems to work without any issues.
c....@gmail.com
Pixel 7 Pro Android 14 Beta 1. Fingerprint setup timed out. Can't use fingerprint sensor. I'm able to unlock phone with other security features but the fingerprint sensor is not working. I've deleted registered fingerprints and tried to register new ones but a pop up error message appears. Attached a screenshot of the message. Fingerprint sensor worked fine before upgrading to Android 14.
c....@gmail.com
It's the same for me. You can't unlock your finger.
is...@google.com
on...@gmail.com
Mine did this once and then suddenly it works again and hasn't happened yet
again. Nothing seemed to trigger it and nothing seemed to fix it either.
Not restarts or anything.
On Wed, Apr 12, 2023, 11:05 PM <buganizer-system@google.com> wrote:
again. Nothing seemed to trigger it and nothing seemed to fix it either.
Not restarts or anything.
On Wed, Apr 12, 2023, 11:05 PM <buganizer-system@google.com> wrote:
vi...@google.com
c....@gmail.com
- Build Number: google/cheetah_beta/cheetah:UpsideDownCake/UPB1.230309.014/9890577:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
I seem to have re-enabled the fingerprint scanning by a combination of removing all fingerprints, disabling face and fingerprint unlock, rebooting and then turning it back on and re-enrolling the fingerprint. Not sure if it is a permanent fix, or what step did the trick. Here is before and after screenshots, note the fingerprint icon.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 556311634 (111.0.5563.116)
System App (Updated)
Network operator: ROGERS
SIM operator: ROGERS
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
I seem to have re-enabled the fingerprint scanning by a combination of removing all fingerprints, disabling face and fingerprint unlock, rebooting and then turning it back on and re-enrolling the fingerprint. Not sure if it is a permanent fix, or what step did the trick. Here is before and after screenshots, note the fingerprint icon.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 556311634 (111.0.5563.116)
System App (Updated)
Network operator: ROGERS
SIM operator: ROGERS
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
vi...@google.com
I tried your solution, it didn't work for me.
hw...@gmail.com
- Build Number: google/cheetah_beta/cheetah:UpsideDownCake/UPB1.230309.014/9890577:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Sorry it didn't work for you. I found that it may be related to the bug entitled "com.android.qns crashed" as it didn't happen on this reboot and may be related.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 556311634 (111.0.5563.116)
System App (Updated)
Network operator: ROGERS
SIM operator: ROGERS
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Sorry it didn't work for you. I found that it may be related to the bug entitled "com.android.qns crashed" as it didn't happen on this reboot and may be related.
Debugging information
Google Play services
com.google.android.gms
Version 231312044 (23.13.12 (190400-519946965))
System App (Updated)
Android System WebView
com.google.android.webview
Version 556311634 (111.0.5563.116)
System App (Updated)
Network operator: ROGERS
SIM operator: ROGERS
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
zu...@gmail.com
I tried your suggestion and it still doesn't work. You may be right about the com.android.ans bug. *shrugs*
ad...@google.com
I can also confirm that my fingerprint reader has stopped working since the update.
Description
API says "End with an 11-character hash string that identifies your app". The problem begins here. Because, according to Turkish laws "If you are a company and you want to send sms your customers, then you need to add a your company code like BXXX to end of sms". Sms looks like this;
There is a conflict here. We need to add company code to the end of sms but API also wants to add hashcode to end of sms. How can we solve this problem? Why should it be in the end? It should be enough to be in sms.