Fixed
Status Update
Comments
le...@gmail.com <le...@gmail.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. OPP1.170223.012)
Which device did you use to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. OPP1.170223.012)
Which device did you use to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
ve...@google.com <ve...@google.com>
ve...@google.com <ve...@google.com> #3
Android version: T
Problem recurrence: Execute Antutu, and pay attention to the XML processing score
Phenomenon: replace the "name expected" in the KXmlParser.java file on the ssi side with a variable. After modification, the XML processing score of Angora Rabbit improved significantly.
Modify to: static final private String NAME_ EXPECTED = "name expected"; And use NAME_ EXPECTED for subsequent "name expected"
Thanks!
ma...@zentity.com <ma...@zentity.com> #5
bugreport has upload. Thankds!
le...@gmail.com <le...@gmail.com> #6
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
jo...@google.com <jo...@google.com> #8
Can you tell us if you have the link to the benchmark tests and the scores BEFORE and AFTER applying this change?
Description
- Reproduced on a device with Android O
I'm providing the source code and an apk that reproduce the issue.
Steps to reproduce:
- Start my apk
- Rotate the screen to landscape when biometric dialog is visible (you can rotate an arbitrary number of times, it doesn't matter)
- Place the fingerprint
- Crash
Sourcecode:
Stacktrace:
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.lithium.leona.openstud, PID: 6782
java.lang.IllegalStateException: Fragment FingerprintDialogFragment{fcd4576 (b3672114-cb16-4247-b15b-c5517c72cc9d)} not associated with a fragment manager.
at androidx.fragment.app.Fragment.requireFragmentManager(Fragment.java:824)
at androidx.fragment.app.DialogFragment.dismissInternal(DialogFragment.java:219)
at androidx.fragment.app.DialogFragment.dismiss(DialogFragment.java:191)
at androidx.biometric.FingerprintDialogFragment.handleDismissDialog(FingerprintDialogFragment.java:334)
at androidx.biometric.FingerprintDialogFragment$H.handleMessage(FingerprintDialogFragment.java:99)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)