Fixed
Status Update
No update yet.
Comments
os...@google.com
al...@google.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.
os...@google.com
ap...@google.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.
ap...@google.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
ap...@google.com
FYI, MDM apps should use DevicePolicyManager.installCaCertificate rather than prompt the user for installation.
ap...@google.com
Please provide the information requested in
os...@google.com
We are closing this issue as we don't have enough actionable information. If you are still facing this problem, please open a new issue and add the relevant information along with reference to earlier issue.
au...@google.com
What is the suggested approach for normal non-MDM applications that want to prompt users to install a CA certificate?
I maintain an Android debugging tool for developers, which acts as a VPN and uses this API to prompt users to install the CA for HTTPS inspection. This is going to break that completely.
Is this change documented somewhere?
I maintain an Android debugging tool for developers, which acts as a VPN and uses this API to prompt users to install the CA for HTTPS inspection. This is going to break that completely.
Is this change documented somewhere?
Description
If you are no longer supporting this library, then follow