- Edited
Why does the “PDF Viewer” always contact “update.vanadium.app” when opening?
The other system apps do not contact anything at all.
Is this really necessary or can it be removed / changed?
Why does the “PDF Viewer” always contact “update.vanadium.app” when opening?
The other system apps do not contact anything at all.
Is this really necessary or can it be removed / changed?
asd
The PDF Viewer is "fed into the sandboxed WebView without giving it access to content or files", which would mean that the check that WebView does described here most likely applies:
Vanadium, our browser and WebView implementation, uses update.vanadium.app to check for updates to components providing revoked certificates and other data. It downloads the components from dl.vanadium.app.
Thanks for the explanation.
But that doesn't clarify why this query is not carried out as part of the central automatic query of all other apps?
asd But that doesn't clarify why this query is not carried out as part of the central automatic query of all other apps?
What central automatic query? This isn't for an app update, it's to update stuff that Vanadium uses. The quoted text that Dumdum provided above says as much: "updates to components providing revoked certificates and other data".
Strange, PDF Viewer does not even have Network permission?
boredace it uses Vanadium WebView which has Network permission. That's what's making those network connections.