Device Explorer stops working for data/data path after upgrade Samsung device to Android 13 [263076528]

Duplicate

of 265653151

Bug

Status Update

No update yet.

Description

to...@gmail.com

created issue #1

Dec 19, 2022 02:04PM

Since the update to A13 Device Explorer stops to showing the content of the data/data folder. At least on Samsung, I'm not sure if it affects another device. It works with the emulator.

I tried to call pm list packages from adb sheell And it fails on java.lang.SecurityException: Shell does not have permission to access user 150

Why it trying to access user 150 by default? 150 is a secure folder on Samsung.

When I explicitly add --user 0 it works.

So the solution is simple, just add --user 0 to the shell call Or allow to manually configure user ID to be used in Device Explorer.

Build: AI-222.4345.14.2221.9321504, 202211222246, 

AI-222.4345.14.2221.9321504, JRE 17.0.4.1+0-b2043.56-9127311x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 2560.0x1440.0, 2560.0x1440.0

AS: Flamingo | 2022.2.1 Canary 9
Kotlin plugin: 222-1.8.0-Beta-release-224-AS4167.29
Android Gradle Plugin: 7.3.1
Gradle: 7.6
Gradle JDK: Eclipse Temurin version 17.0.3

image (3).png

69 KB

View

Download

Comments

ri...@google.com <ri...@google.com> Dec 20, 2022 10:24AM

Assigned to an...@google.com.

sp...@google.com <sp...@google.com> Dec 21, 2022 10:43PM

Reassigned to ch...@google.com.

sa...@google.com <sa...@google.com> #2Jan 18, 2023 10:46PM

I just tried on a Pixel running Android 13 and adb shell pm list packages worked. The issue may be related to Samsung build. Tomas, can you attach the output of adb shell getprop | grep "ro." to this bug?

to...@gmail.com <to...@gmail.com> #3Jan 19, 2023 08:12AM

Here is the requested shell call.

ro.txt

21 KB

View

Download

sa...@google.com <sa...@google.com> Jan 19, 2023 07:34PM

Status: Duplicate of

265653151

to...@gmail.com <to...@gmail.com> #4Jan 19, 2023 10:16PM

I never understood how my older issue could be a duplicate of the newer issue. And especially when it has much less information in the description. But I'm not angry about that, just interested ;-)

sa...@google.com <sa...@google.com> #5Jan 19, 2023 10:37PM

The other bug entry does mention that the issue is related to Samsung "Secure Folder" feature so I elected to close this one.

to...@gmail.com <to...@gmail.com> #6Jan 20, 2023 11:25AM

In mine is also mentioned "secure folder" ;-). But OK it doesn't matter, the most important is, if it will be possible to fix it.