IssueTracker

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 find here the demonstration video: https://drive.google.com/open?id=15PEkr6H-LZehyGfNaq2iiLC317wpOSIJ
Bugreport: https://drive.google.com/open?id=1dwg-VMhIsLxTFnkCd4A-OLQPEaknj9ld

I am working on creating test account that you can use to reproduce the problem.

Thanks.

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. Enter eapp069.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.

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.

FYI, MDM apps should use DevicePolicyManager.installCaCertificate rather than prompt the user for installation.

Please provide the information requested in comment #5

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.

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?

Non-MDM apps could, for example, take the following approach:
* Write the CA certificate to the Download media collection.
* Prompt the user to go to Settings to install the certificate from the Download media collection.

The functionality of installing a CA certificate manually by the user isn't going away. But to make sure the user gets adequate explanation on the implications, this is only possible via settings. See bug 139153251.

البطاريه لاتشحن تظهر لي علامة حرارة الهاتف مرتفعه والجواب له اسبوع مقفل ولايقبل الشحن

Is this getting fixed?  Just curious, trying to stay loyal to Android :-)

I can't select a certificate from my files

Request you to raise a new bug if it exists in recent releases.
Thanks.

CA certificates are used by websites, apps and VPNs for encryption. Only install CA certificates from organisations that you trust.

If you install a CA certificate, the certificate owner could access your data, such as passwords or credit card details, from websites that you visit or apps that you use even if your data is encrypted.

Your data won't be private

CA certificates are used by websites, apps, and VPNs for encryption. Only install CA certificates from organizations you trust.

If you install a CA certificate, the certificate owner could access your data, such as passwords or credit card details, from websites you visit or apps you use even if your data is encrypted.