The obvious way to avoid driving the app for #226 was a host Activity in androidTest owning its own CreateDocument launcher. It cannot be started at all:
RuntimeException: Intent in process org.libremediaconverter resolved to different
process org.libremediaconverter.test
Instrumentation runs in the target app's process, so a component declared in the instrumentation APK is in the wrong one — the same fact as E7's second bullet, arriving from the other side. That leaves the app's own Save button as the only launcher available to drive, which is also the more faithful thing to drive.
And the premise held
The question #226 was filed for: on API 34, stock DocumentsUI hands back a document URI reporting a size of exactly zero. So destinationIsKnownEmpty can return true, deletePartialOutput can fire, and D4's fix is live rather than inert.
A "no defect found" — and not one that could have been reached by reading, which is the argument for having done it.
Documentation only, closing the loop on #226.
## A second constraint, same cause
The obvious way to avoid driving the app for #226 was a host Activity in `androidTest` owning its own `CreateDocument` launcher. It cannot be started at all:
```
RuntimeException: Intent in process org.libremediaconverter resolved to different
process org.libremediaconverter.test
```
Instrumentation runs in the **target app's** process, so a component declared in the instrumentation APK is in the wrong one — the same fact as E7's second bullet, arriving from the other side. That leaves the app's own Save button as the only launcher available to drive, which is also the more faithful thing to drive.
## And the premise held
The question #226 was filed for: on API 34, stock DocumentsUI hands back a document URI reporting a size of **exactly zero**. So `destinationIsKnownEmpty` can return true, `deletePartialOutput` can fire, and D4's fix is **live rather than inert**.
A "no defect found" — and not one that could have been reached by reading, which is the argument for having done it.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Documentation only, closing the loop on #226.
A second constraint, same cause
The obvious way to avoid driving the app for #226 was a host Activity in
androidTestowning its ownCreateDocumentlauncher. It cannot be started at all:Instrumentation runs in the target app's process, so a component declared in the instrumentation APK is in the wrong one — the same fact as E7's second bullet, arriving from the other side. That leaves the app's own Save button as the only launcher available to drive, which is also the more faithful thing to drive.
And the premise held
The question #226 was filed for: on API 34, stock DocumentsUI hands back a document URI reporting a size of exactly zero. So
destinationIsKnownEmptycan return true,deletePartialOutputcan fire, and D4's fix is live rather than inert.A "no defect found" — and not one that could have been reached by reading, which is the argument for having done it.
🤖 Generated with Claude Code