IssueTracker

Hi, thanks for the answer!

The issue happens when I create a new release in the Google Play Console, after Firebase Test Lab has run to generate the pre-launch report (see screenshots shared). The only device affected, 1 out of 8, is the samsung SM-G981U1. I cannot recreate it on my devices, nor in the emulator, so the main problem I see is releases getting blocked because of this.

The issue seems to be related to a recent version of Firebase. I've also shared the pre-launch report video and the LogCat via Google Drive.

Here is the link to the Google Drive folder.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

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

Hi, it only happens in the Firebase Test Lab running for the pre-launch report, I already shared the output I get and I can't access the emulator you run there to capture a bug report.

By the way, this did not prevent my app from getting published.

Same thing here:

Exception Process: com.google.android.apps.mtaas.deviceadmin, PID: 4528
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:2209)
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:7218)
  at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanManageScope (DevicePolicyManagerService.java:7204)

Device specifications

Model name: SM-G981U1

Manufacturer: samsung

Android version: Android 10 (SDK 29)

Locale: en_GB

Screen size: 1440 x 3200

Screen density (DPI): 480

RAM (total memory): 12,288 MB

OpenGL ES version: 3.2

ABI: arm64-v8a

Thanks for reporting this issue!

Are you able to reproduce this issue on a non-Samsung device? If so, it would be helpful to get a bug report.

From the attached logs, it looks like there is no active admin associated with the component com.google.android.apps.mtaas.deviceadmin/com.google.android.apps.mtaas.deviceadmin.DeviceAdminReceiver.

Was the app (with package name com.google.android.apps.mtaas.deviceadmin) correctly provisioned?

Please can we get more detailed reproduction steps?

Thanks!

Please can we get more detailed reproduction steps?

I see this in the play console pre-launch report. The reproduction step is - upload my ordinarily fine app, and then witness this crash. From https://issuetracker.google.com/issues/160907013#comment289 this comment onward there are a lot more people reporting the same.

Re-comment#19, comment#22, comment#24, Thanks for the update. As requested in comment#18, please share a bugreport that will help us in investigating the issue further.

Other affected users, please share the reproduction information and a bugreport as requested in comment#18.

Re-comment#28: A bugreport contains device logs, stack traces, and other diagnostic information. To capture a bug report from your device, use the Take bug report developer option on the device, the Android Emulator menu, or the adb bugreport command on your development machine. For details you may refer to this link.

We have already shared the above comments and query with our development team and will update on this with more information as it becomes available.

Will this error prevent me from pushing my app to live production if I just ignore it?

Meanwhile, if you can share a bugreport would be great as it may help our development team to investigate.

This issue happend on our PLR before, and disappered,and now it occurs again.

Re #29: please don't keep asking developers for bugreports. If you read the previous comments (such as #28) carefully, this issus happens on Google Play PLR (Pre-launch report), meaning that Google Play's internal testing system is causing the problem. You could query the recently generated Google Play PLRs for this issue, then identify and fix the underlying problem, so that PLRs won't generate false alarms and waste many app developers' time, thanks.

i met same issue,I think that internal testing system is causing the problem Can i ignore it before deploy?

This has been fixed by our development team, Thanks!