Fixed
Status Update
No update yet.
Comments
cz...@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.
ap...@google.com
na...@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.
[Deleted User] <[Deleted User]>
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
na...@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
Description
$ gcloud sql instances patch --database-flags max_connections=5000 [instance-name]
The following message will be used for the patch API method.
{"project": "test-waffle-381", "name": "[instance-name]", "settings": {"databaseFlags": [{"name": "max_connections", "value": "5000"}]}}
WARNING: This patch modifies a value that requires your instance to be restarted. Submitting this patch will immediately restart your instance if it's running.
Do you want to continue (Y/n)?
What you expected to happen:
Flag should be applied dynamically with no instance restart.
Other information:
max_connections flag is in beta, and should be not used in production environment