Fixed
Status Update
Comments
ro...@google.com <ro...@google.com> #2
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.
ch...@google.com <ch...@google.com> #3
ro...@google.com <ro...@google.com>
ch...@google.com <ch...@google.com> #4
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.
ch...@google.com <ch...@google.com> #5
Sorry for late reply. If you are still facing this issue with latest Android 11 beta then please share video & bug report.
Links in comment #3 & credentials in comment #4 are not working.
Links in
ch...@google.com <ch...@google.com> #6
FYI, MDM apps should use DevicePolicyManager.installCaCertificate rather than prompt the user for installation.
go...@google.com <go...@google.com> #7
Please provide the information requested in comment #5
Description
This is an M136 merge request from crbug/381687257. The following changes were detected on the parent issue:
To proceed with this merge request:
Safe Merge Criteria
Please only select Yes in the Safe Merge field if all the following apply:
Please contact the milestone owner if you have questions.
Owners: andywu (ChromeOS), srinivassista (Desktop US), danielyip (Desktop EMEA), govind (Mobile US), eakpobaro (Mobile EMEA)
*Find more information on Chrome/Chromium's merge process at go/chrome-merge-process and Chromium Docs - Merge Request Process