Can't Repro
Status Update
Comments
lo...@gmail.com <lo...@gmail.com> #2
Information redacted by Android Beta Feedback.
jv...@google.com <jv...@google.com>
ac...@google.com <ac...@google.com> #3
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.
xa...@google.com <xa...@google.com> #4
- 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
lo...@gmail.com <lo...@gmail.com> #5
Information redacted by Android Beta Feedback.
ga...@google.com <ga...@google.com> #6
Same issue and it also will not allow me to register new fingerprints. Android 14 Beta 1
lo...@gmail.com <lo...@gmail.com> #7
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.
ga...@google.com <ga...@google.com> #8
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.
lo...@gmail.com <lo...@gmail.com> #9
It's the same for me. You can't unlock your finger.
ga...@google.com <ga...@google.com> #10
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:
lo...@gmail.com <lo...@gmail.com> #11
- 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
an...@google.com <an...@google.com> #12
I tried your solution, it didn't work for me.
Description
The (critical) problem:
Android Studio Arctic Fox 2020.3.1 Arctic Fox Canary 3 (and Canary 1 & Canary 2) and the Android Gradle Plugin version 7.0.0-alpha03 (and alpha 02 and 03) don't deploy changes in code, as value changes of compile time constants are not reflected when running the app after a change: the old value is still used.
I witnessed the issue on a Google Pixel 2 XL running the very latest Android 11 (with the "final" update that came after it'd say there would not be further updates).
I've been able to catch it because I enabled network logging and had to change the baseUrl. I suspect many people think they are going crazy or that their app or device is broken while it is "just" that their changes are not being deployed.
I don't know if it only affects changes to values of constants, and I don't know if it affects all Android versions, some Android versions (like 8+) or only Android 11.
That critical bug can be seen whether you use the green triangle "Run" button or if you run the
installDebug
Gradle task from the Gradle tool window. It might also happen from command line (where there's no IDE injected properties).Also, note that I tested it through Wireless debugging that I paired in the command line without plugging the device while the UI to do it was missing in the first 2020.3.1 Canary.
Steps to Reproduce:
const val one = 1; const val two = 2
const val current = one
onCreate
):Log.d("CURRENT", current)
1
for the "CURRENT" tag.current
so it referencestwo
instead ofone
:const val current = two
Expected result:
You see
2
for the "CURRENT" tag in the logs, reflecting the changes.Actual result:
You see
1
for the "CURRENT" tag in the logs, showing it didn't deploy the changes or a new app.Side effects:
I want to smash my poor computer that just did what he was asked for by the programs.
Trust issues introduced in AS Arctic Fox
This issue really worrying and disrupting, I cannot trust code deployed by AGP 7 or AS Arctic Fox at all so far:
I tried to uninstall my app and reinstall with the IDE, and the issue is still there 😓
I changed a constant (the baseUrl for a server) to reference another constant with a different value, and it didn't take the change into account despite the uninstall.
I hope the "Instant Run" nightmare isn't having a second season.
IDE info