search

GrapheneOS / Vanadium

Privacy and security enhanced releases of Chromium for GrapheneOS. Vanadium provides the WebView and standard user-facing browser on GrapheneOS. It depends on hardening in other GrapheneOS repositories and doesn't include patches not relevant to the build targets used on GrapheneOS.
https://vanadium.app/
Other
870 stars 69 forks source link

Media picker can't access screenshots after they have been edited by stock Gallery app #622

Open Saroumane opened 5 days ago

Saroumane commented 5 days ago

Phone : Pixel 6a GrapheneOS build 2024091900

Steps to reproduce :

  1. Make a screenshot (Vol Down + Lock button)
  2. Open stock Gallery app, edit the screenshot, save
  3. Open stock Vanadium app, go to x.com, start a post, clic on the button to add a picture
  4. the Media picker is started, on default tab "Photos", "Recent". The edited screenshot is missing.
  5. Clic on "Albums" tab, then on "Screenshots" album. The edited screenshot is still missing.

Verification 1 : Go to Settings / Apps, then "show system apps", choose "Media picker" All values are on default. Permissions say "Allowed : Notifications, Sensors". Not allowed : No permissions denied.

Verification 2 : Redo Steps 1 - 5, minus step 2. The (unedited) screenshot is both present in Photos / Recent and Albums / Screenshot (from Media picker)

Saroumane commented 4 days ago

"thestinger transferred this issue from GrapheneOS/os-issue-tracker" So the media picker is part of Vanadium ? Or it "inherits" permissions from the calling app ? I'm trying to understand.

It made me try to reproduce the problem with a different app : I have done again all steps, replacing Vanadium by "Contacts" stock app. And indeed the edited screenshot can be selected ! So it really looks like a Vanadium issue, despite my Vanadium app having "Always allow all" for the "Photos and Videos" permission.

thestinger commented 4 days ago

It's a Chromium limitation Vanadium inherits from it from how it's using this.

thestinger commented 4 days ago

We don't know the details but have seen it before. I don't see an existing issue but often things are reported in the chat rooms and forum rather than the issue trackers. It's also often not clear if something is a bug or by design. Chromium may be intended to work the way it does but we could change it slightly.