No active admin [286438667]

Duplicate

of 287304300

Bug

Status Update

No update yet.

Description

dh...@gmail.com

created issue #1

Jun 9, 2023 08:19AM

stack traces given at time of pre-launch report

java.lang.SecurityException: No active admin ComponentInfo{com.google.android.apps.mtaas.deviceadmin/com.google.android.apps.mtaas.deviceadmin.DeviceAdminReceiver}

this is full log cat

ATAL EXCEPTION: Instr: com.google.android.apps.mtaas.deviceadmin.EnableNetworkLogging Process: com.google.android.apps.mtaas.deviceadmin, PID: 1996 java.lang.SecurityException: No active admin ComponentInfo{com.google.android.apps.mtaas.deviceadmin/com.google.android.apps.mtaas.deviceadmin.DeviceAdminReceiver} at android.os.Parcel.createException(Parcel.java:2088) at android.os.Parcel.readException(Parcel.java:2056) at android.os.Parcel.readException(Parcel.java:2004) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setNetworkLoggingEnabled(IDevicePolicyManager.java:15305) at android.app.admin.DevicePolicyManager.setNetworkLoggingEnabled(DevicePolicyManager.java:11627) at com.google.android.apps.mtaas.deviceadmin.EnableNetworkLogging.onStart(EnableNetworkLogging.kt:27) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2214) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminWithPolicyForUidLocked(DevicePolicyManagerService.java:3259) at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminOrCheckPermissionForCallerLocked(DevicePolicyManagerService.java:3155) at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminForCallerLocked(DevicePolicyManagerService.java:3136) at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanManageScopeOrCheckPermission(DevicePolicyManagerService.java:7206) at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanManageScope(DevicePolicyManagerService.java:7192)

now I am not able to understand what really i need to do.

Comments

ra...@google.com <ra...@google.com> #2Jun 9, 2023 09:47AM

Assigned to ra...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Steps to reproduce
What steps are needed to reproduce this issue?

Android build
Which Android build are you using? (e.g. OPP1.170223.012)

Device used
Which device did you use to reproduce this issue?

Related API or developer doc.

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 bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.

ch...@gmail.com <ch...@gmail.com> #3Jun 12, 2023 04:35PM

This error occured in pre-release report in samsung device. can you give me explanation.

ra...@google.com <ra...@google.com> #4Jun 16, 2023 03:45AM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

ke...@gmail.com <ke...@gmail.com> #5Jun 18, 2023 10:59AM

The test device is chosen by Google Play's test lab (to produce the pre-launch report), NOT app developer. Please just run a query of recently generated Google Play pre-launch reports, and I'm sure you'll see many cases of this error.

For our case, it's samsung SM-G981U1, screen size 1440x3200, running Android 10 (SDK 29), with RAM 12,288 MB, ABI arm64-v8a, locale it_IT.

ke...@gmail.com <ke...@gmail.com> #6Jun 19, 2023 02:47AM

Hi Googler assignee: you may want to consult FTL (Firebase Test Lab) team if the tests in PLR were actually conducted by them.

su...@gmail.com <su...@gmail.com> #7Jun 19, 2023 02:51AM

Pada tanggal Sen, 12 Jun 2023 23.35, <buganizer-system@google.com> menulis:

- Show quoted text -

su...@gmail.com <su...@gmail.com> #8Jun 19, 2023 02:52AM

Pada tanggal Sen, 19 Jun 2023 09.51, Sudarmanto Ronaldo <
sudarmantoronaldo@gmail.com> menulis:

- Show quoted text -

sh...@gmail.com <sh...@gmail.com> #9Jun 19, 2023 02:59AM

Game space not open

ke...@gmail.com <ke...@gmail.com> #10Jun 19, 2023 03:01AM

Update on our side (an 3p app): in the newly generated PLR (Jun 18, 23:57pm) of the latest uploaded app version, this error disappeared! I guess the underlying problem has been fixed, but would like Google Play team to confirm it, and/or other 3p apps developers to verify it. :)

ra...@google.com <ra...@google.com> Jun 19, 2023 05:47AM

Status: Duplicate of

287304300