"Missing dependency" error on trying to update disabled Google Play about apps HOT 10 CLOSED

I saw another notification, IIRC "Updates available". This caused me to open Apps, where I was able to manually update the Vanadium group.

What I meant is that "Updates available" notification being shown doesn't mean that auto-update is broken.
Since version 18, auto-update happens only when the device is idle, but update check can happen at any time. Update check is what produces the "Updates available" notification.

from apps.

This situation also blocked the automatic update of other apps unrelated to Google Play (Vanadium + Trichrome Library + Vanadium System WebView), although it was possible to update these manually.

from apps.

Interestingly it did not block the recent automatic updates of Camera and Auditor.

from apps.

This situation also blocked the automatic update of other apps unrelated to Google Play (Vanadium + Trichrome Library + Vanadium System WebView)

How did you determine that auto-update of Vanadium group was blocked by this issue?

from apps.

@muhomorr It was after muting the "Missing dependency" notification channel to get rid* of Google Play related noise. I saw another notification, IIRC "Updates available". This caused me to open Apps, where I was able to manually update the Vanadium group. (If it happens again I'll pay closer attention to the exact notification details.)

No idea why it would block automatic updates of the Vanadium group but not Camera or Auditor. Maybe if something has dependencies at all (even if they're satisfiable), dependency resolution can fail if there's a dependency problem anywhere else? Assuming that it wasn't a network related fluke.

* Get rid of it as a notification. Whenever I occasionally open Apps, there'll still be a dozen or so "Missing dependency" popups stacked on top of each other, probably a new one after each update check.

from apps.

Vanadium auto update is not blocked by this issue.

Since version 18, app update check happens separately from app auto-update, see https://github.com/GrapheneOS/Apps/releases/tag/18

from apps.

This time the Vanadium auto update was successful (to v113.0.5672.62.1). I'm still puzzled about what happened last time. Anyway, sorry for the noise.

from apps.

auto-update happens only when the device is idle, but update check can happen at any time.

Ah, that makes sense! Thank you. I really should have re-read the release notes.

from apps.

In this code block where the error seems to originate, a package state's raw osPackageInfo is checked to see if it's enabled. Should its status() be checked instead? IIUC that would treat a disabled package as enabled when canUpdateDisabledPackages is true.

from apps.

Should its status() be checked instead?

No, fresh installation of package that depends on disabled package should fail.

from apps.