Auto-discovery only works for apps that can see Veil: on Android 11+ an
app without QUERY_ALL_PACKAGES (or a matching <queries>) can't resolve
Veil's provider, so its first-launch check-in silently fails. A real app hit this: scoped and hooked, but never listed. That made 615f000's premise,
that auto-detection covers every target, wrong.
- "Add app" opens a searchable list of launchable apps; picking one saves
its default feature set, which is what gives an app a card. A
launcher-intent <queries> is enough for this and narrower than
QUERY_ALL_PACKAGES; it widens what Veil sees, not who sees Veil.
- App cards show the app's label above the package name.
- reportScoped checks resolveContentProvider first and skips the call
when Veil isn't visible. That also drops the framework's
"Failed to find provider info for space.bdeshi.veil.provider" line,
which named Veil in the target's own, app-readable logcat.
- New help tip explains why a scoped app may not show up.
Verified on device (Android 16, Vector): a scoped app no longer logs the
provider failure, and adding it through the picker saves its feature set.
Co-Authored-By: agent <agent@bdeshi.space>
bdeshiandagent
af97a85c54