Release persistable URI grants when file references are removed #20

New issue

Open

opened 2026-09-16 21:54:50 +02:00 by morten-olsen · 0 comments

morten-olsen commented

2026-09-16 21:54:50 +02:00

Owner

FileReferenceAccess.takePersistableRead takes a long-lived read grant when the user picks a document, but nothing ever
releases it. Deleting the node, or the whole workflow, leaves the grant behind.

Releasing precisely needs a reconcile pass over every stored workflow to find which references are still live before
calling releasePersistableUriPermission, which is the same ownership-derived shape BackgroundResourceManager already
uses for platform registrations rather than a second inventory.

Consequences today are bounded: grants are per-document and Android caps how many an app may hold, so this is untidy
rather than harmful. Worth fixing before file references spread beyond audio.play.

`FileReferenceAccess.takePersistableRead` takes a long-lived read grant when the user picks a document, but nothing ever releases it. Deleting the node, or the whole workflow, leaves the grant behind. Releasing precisely needs a reconcile pass over every stored workflow to find which references are still live before calling `releasePersistableUriPermission`, which is the same ownership-derived shape `BackgroundResourceManager` already uses for platform registrations rather than a second inventory. Consequences today are bounded: grants are per-document and Android caps how many an app may hold, so this is untidy rather than harmful. Worth fixing before file references spread beyond `audio.play`.

morten-olsen added the

feature

label

2026-09-17 08:19:57 +02:00