Status Update
No update yet.
Comments
tr...@gmail.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
ve...@google.com
ve...@google.com
tr...@gmail.com
I created a test account that you can use. These are the steps.
1. Please install Mobile@Work from Google Play.
2. To register please launch it and tap on "Or register with server URL"
3. Entereapp069.auto.mobileiron.com as server URL.
4. On next screen enter user name test and password Qwerty12
5. Go though provisioning, acquiring Device Admin, grant or deny location permission.
6. Certificate provisioning will start and you will see the issue.
1. Please install Mobile@Work from Google Play.
2. To register please launch it and tap on "Or register with server URL"
3. Enter
4. On next screen enter user name test and password Qwerty12
5. Go though provisioning, acquiring Device Admin, grant or deny location permission.
6. Certificate provisioning will start and you will see the issue.
tr...@gmail.com
Sorry for late reply. If you are still facing this issue with latest Android 11 beta then please share video & bug report.
Links in
Links in
Description
What
User experience
What type of Android issue is this?
User Interface
What steps would let us observe this issue?
What did you expect to happen?
It should be consistent and repeatable
What actually happened?
Behavior is inconsistent, making phone hard to use
What was the effect of this issue on your device usage, such as lost time or work?
High
When
Time and frequency
How often has this happened?
Every time
Where
Component
Originating component: <not visible> (1684638)
Build and device data
- Build Number: google/komodo_beta/komodo:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)
Network operator: Visible
SIM operator: Visible
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