How do you request MANAGE_EXTERNAL_STORAGE permission in Wear OS? [267354973]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

di...@gmail.com

created issue #1

Feb 1, 2023 07:43AM

In Android 11+, I use : try { Log.d(TAG, "requestPermission: try");

                Intent intent = new Intent();
             intent.setAction(Settings.ACTION_MANAGE_APP_ALL_FILES_ACCESS_PERMISSION);
                Uri uri = Uri.fromParts("package", this.getPackageName(), null);
                intent.setData(uri);
                startActivityForResult(intent,111);
            }
            catch (Exception e){
                Log.e(TAG, "requestPermission: catch", e);
                Intent intent = new Intent();
                intent.setAction(Settings.ACTION_MANAGE_ALL_FILES_ACCESS_PERMISSION);
                startActivityForResult(intent,222);
            }

But error : android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.MANAGE_APP_ALL_FILES_ACCESS_PERMISSION

Comments

vi...@google.com <vi...@google.com> #2Feb 1, 2023 10:40AM

Assigned to vi...@google.com.

Android 5.0, 5.1: it shows context menu at top of screen, not as popup. See screenshots.

Android framework doesn't support floating toolbar before 23. So this is intended behavior.

The crash information suggests that this is an error from Snapshot. chuckj@ can you please take a look? I don't know what exactly caused the readError in Snapshot, any suggestions? Thanks a lot!

se...@gmail.com <se...@gmail.com> #3Apr 14, 2023 11:11AM

This looks like another instance of 193006595 which I am looking at now.

ar...@gmail.com <ar...@gmail.com> #4Apr 15, 2023 05:10AM

Project: platform/frameworks/support
Branch: androidx-main

commit beeb84e7be604088ad40e080a8d0adb1bacbf695
Author: Chuck Jazdzewski <chuckj@google.com>
Date: Thu Jul 08 10:04:28 2021

Remove updating the transparent snapshot

A transparent snapshot is create for the block exeucted by
`Snapshot.observe()` which registers read and write observers
but without creating a snapshot. The code to advance the
global snapshot, however, created a new transparent snapshot in
an attempt to update it to the new global snapshot it just
created. This is not necessary, however, as the transparent
snapshot will retrieve the current global snapshot from
`currentGlobalSnapshot` instead of `previousSnapshot` if
`previousSnapshot` is `null`. With the previous code, if the
global snapshot is advanced by applying a new snapshot the
"updated" transparent snapshot will be left referring to an
older snapshot instead of the most recent global snapshot.
Any snapshot object created in the newly applied snapshot
will throw an exception when it is accessed, as reported in
the bugs. The solution is to remove the apparent vetiagal code.

Test: ./gradlew :compose:r:r:tDUT
Fixes:

b/193006595

b/192570897

Change-Id: I2c0d0b8f57bf70e5a98ea36ed141d97142a5e53e

M compose/runtime/runtime/src/commonMain/kotlin/androidx/compose/runtime/snapshots/Snapshot.kt
M compose/runtime/runtime/src/test/kotlin/androidx/compose/runtime/snapshots/SnapshotTests.kt

https://android-review.googlesource.com/1760301

do...@gmail.com <do...@gmail.com> #5Nov 16, 2023 04:55AM

I'm facing the same problem here... any solution?

ak...@google.com <ak...@google.com> #6Jan 18, 2024 11:21AM

I hit the same thing on Wear, as a workaround until there is a way to achieve this programmatically this permission can be granted via adb:

adb shell appops set --uid PACKAGE_NAME MANAGE_EXTERNAL_STORAGE allow

ar...@gmail.com <ar...@gmail.com> #7Jan 18, 2024 03:21PM

#6: Thank you, but specially on Android TV, asking users to do this is going to cause a lot of confusion since they would need to connect with a PC of some sort and it's not trivial.

Now that this issue is on Google's radar, is it possible to gain some momentum and still patch existing Android versions?

so...@google.com <so...@google.com> #8Jan 19, 2024 10:55AM

There are no TV devices on Android 13, as we will go from Android 12 -> Android 14 for TV devices. So I am not sure how this was tested on Android 13 for TV. We will check if this has been fixed on Android 14 for TV and then back port to older versions.

ar...@gmail.com <ar...@gmail.com> #9Jan 19, 2024 11:22PM

#8 I believe #3 tested it on an emulator, since there's an Android TV 13 image available.

Thank you for checking on backporting. Since we believe it was fixed in A13, it's a matter of figuring out how to backport to A11/A12 and releasing for existing devices.

so...@google.com <so...@google.com> #10Feb 9, 2024 09:42AM

Ok. We have completed the backporting to R and S on TV

13...@qq.com <13...@qq.com> #11Feb 26, 2024 08:37AM

Hello, may I ask how to solve this problem on WearOS4? The watch file manager I developed is not working properly.

ar...@gmail.com <ar...@gmail.com> #12May 16, 2024 09:21PM

I'm happy to report that the latest update to Chromecast with Google TV (still Android 12) fixes the issue, and now the "install unknown apps" permission screen shows up correctly and our app can be selected. Thank you to all involved who backported the fix.

vi...@google.com <vi...@google.com> #13Jun 30, 2024 01:47PM

Marked as fixed.

The issue has been fixed and watch out for future releases.

hi...@gmail.com <hi...@gmail.com> #14Jul 19, 2024 06:44PM

Hello,
Where can I get the release with the fix for Wear OS? I am in a hurry to release an app.

Thanks

13...@qq.com <13...@qq.com> #15Aug 11, 2024 02:34AM

I also encountered the same problem. I developed a file manager, but users cannot use my file manager properly on the new version of the watch.

he...@gmail.com <he...@gmail.com> #16Aug 12, 2024 04:02AM

The fix that is backported is not for Wear OS but for TV. I'm not sure when they will be fixing the issue on Wear OS.

ko...@gmail.com <ko...@gmail.com> Dec 15, 2024 06:22AM

deleted

Restricted

0 B

ar...@gmail.com <ar...@gmail.com> #17Mar 28, 2025 08:23PM

Please fix this for Wear OS as well, which was the original reported target OS.

IssueTracker