GrapheneOS/Vanadium

Cannot apply update

newhinton opened this issue · 17 comments

Hello!

At the moment, when i try to update vanadium via "Apps", i randomly get one of two error messages (attached below). I have tried deleting app and userdata for vanadium itself, but that did't help. I cant see any pattern to which error message is shown. I have also attached a logcat snippet with the relevant logs.

On a different topic:
I have been using grapheneos for quite a while now, and this is the first actual "bug" that i encountered. This project is impressively stable and i am very happy to use it. Thank you for all your work!

If this is the wrong issue tracker, please guide me to the right one and i will file a bug there. Also if you need additional information, i am happy to try to provide it.

Error Message 1:

Unable to install Vanadium, Trichrome Library.

Details: 
0

Error Message 2:

Unable to install Vanadium, Trichrome Library: package conflicts with another package that is already installed on this device.

Details: 
INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated
Logcat:

2024-04-13 08:58:38.228 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:f41db1ac: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_FROM_VIEW
2024-04-13 08:58:38.228 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:f41db1ac: onFailed at PHASE_CLIENT_VIEW_SERVED
2024-04-13 08:58:38.228 14867-14867 InputMethodManager      app.grapheneos.apps                  W  Ignoring hideSoftInputFromView() as view=com.google.android.material.button.MaterialButton{e57b0ef VFED..C.. ......ID 21,0-975,126 #7f0901b4 app:id/secondary_action_btn} is not served.
2024-04-13 08:58:38.529 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:a8e36048: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_FROM_VIEW
2024-04-13 08:58:38.529 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:a8e36048: onFailed at PHASE_CLIENT_VIEW_SERVED
2024-04-13 08:58:38.529 14867-14867 InputMethodManager      app.grapheneos.apps                  W  Ignoring hideSoftInputFromView() as view=com.google.android.material.button.MaterialButton{e57b0ef VFED..C.. ......ID 21,0-975,126 #7f0901b4 app:id/secondary_action_btn} is not served.
2024-04-13 08:58:38.646  1403-1896  PackageInstallerSession system_server                        E  mUserActionRequired should not be null.
2024-04-13 08:58:38.646  1403-1896  PackageInstallerSession system_server                        E  mUserActionRequired should not be null.
2024-04-13 08:58:38.648  1403-1706  PackageManager          system_server                        E  No required verifiers
2024-04-13 08:58:38.650  1403-1706  PackageManager          system_server                        E  No required verifiers
2024-04-13 08:58:38.657  1403-1936  RuleEvaluation          system_server                        W  Integrity rule files are not available.
2024-04-13 08:58:38.657  1403-1706  PackageManager          system_server                        I  Integrity check passed for file:///data/app/vmdl454363684.tmp
2024-04-13 08:58:38.678  1403-1936  RuleEvaluation          system_server                        W  Integrity rule files are not available.
2024-04-13 08:58:38.678  1403-1706  PackageManager          system_server                        I  Integrity check passed for file:///data/app/vmdl1861109981.tmp
2024-04-13 08:58:38.829 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:434a7abc: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_FROM_VIEW
2024-04-13 08:58:38.829 14867-14867 ImeTracker              app.grapheneos.apps                  I  app.grapheneos.apps:434a7abc: onFailed at PHASE_CLIENT_VIEW_SERVED
2024-04-13 08:58:38.829 14867-14867 InputMethodManager      app.grapheneos.apps                  W  Ignoring hideSoftInputFromView() as view=com.google.android.material.button.MaterialButton{e57b0ef VFED..C.. ......ID 21,0-975,126 #7f0901b4 app:id/secondary_action_btn} is not served.
2024-04-13 08:58:38.874  1403-1706  PackageManager          system_server                        W  Packages declaring static-shared libs cannot be updated
2024-04-13 08:58:38.874  1403-1647  ActivityManager         system_server                        I  Force stopping app.vanadium.trichromelibrary_631211833 appid=10284 user=-1: installPackageLI
2024-04-13 08:58:38.875  1403-1647  libprocessgroup         system_server                        E  No such cgroup attribute: /sys/fs/cgroup/uid_4294877580/cgroup.freeze
2024-04-13 08:58:38.875  1403-1647  libprocessgroup         system_server                        W  Failed to apply Frozen process profile: No such file or directory
2024-04-13 08:58:38.878  1403-1706  PackageInstallerSession system_server                        D  Marking session 1794826153 as failed: INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated
2024-04-13 08:58:38.878  1403-1706  PackageInstallerSession system_server                        I  Session [1794826153] was destroyed because of [Session marked as failed: INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated]
2024-04-13 08:58:38.878  1403-1706  PackageInstallerSession system_server                        I  Session [454363684] was destroyed because of [Session marked as failed: INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated]
2024-04-13 08:58:38.878  1403-1706  PackageInstallerSession system_server                        I  Session [1861109981] was destroyed because of [Session marked as failed: INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated]
2024-04-13 08:58:38.880  1403-1647  libprocessgroup         system_server                        E  No such cgroup attribute: /sys/fs/cgroup/uid_4294877580/cgroup.freeze
2024-04-13 08:58:38.880  1403-1647  libprocessgroup         system_server                        W  Failed to apply Unfrozen process profile: No such file or directory
2024-04-13 08:58:38.910 14867-14867 InstallerS...onCallback app.grapheneos.apps                  D  completed multi-install session 1794826153, success: false
2024-04-13 08:58:38.910 14867-14867 InstallerS...onCallback app.grapheneos.apps                  D  completed session 454363684, success: false
2024-04-13 08:58:38.910 14867-14867 InstallerS...onCallback app.grapheneos.apps                  D  completed session 1861109981, success: false

Environment:

Device: Pixel 7
OS: GrapheneOS 14
Patchlevel: 05.04.204
Buildnumber: 2024040900
"Apps"-Version: 22
Vanadium: 123.4.6312.99.0 (Avaliable update: 123.0.6312.118.0)
Trichrome: 123.0.6312.118.0 (it seems to be not installed?)

This is currently what happens if you update one but not the other in a user profile. Update it from the user profile you started updating it.

I was able to update the workprofile's trichrome app to 124.0.6367.42.0, but not the main profile-one.

It now shows that the 124.* version of vanadium is available, but installing it results in the same error.

I also cannot find the package in the apps, to remove&reinstall it, so i am kinda confused about what to do.

I was able to update the workprofile's trichrome app to 124.0.6367.42.0, but not the main profile-one.

They aren't updated separately.

I also cannot find the package in the apps, to remove&reinstall it, so i am kinda confused about what to do.

You updated the WebView without updating the browser. Update the browser where you updated the WebView. It's a known limitation of the current app repository client. Update both in the same place.

I guess i accidentially updated the webview from the work-profile. That doesn't have vanadium, only the webview&the library.

I can "uninstall updates" and replace it with the factory-version via the settings, would that allow me to "switch" updates back to the main profile?

Yes, at least after a delay for the newer version of the library to get removed.

That seems to have worked, thank you!

Hi,
I've got the same issue, but I don't seem to be able to uninstall updates (or just don't know how...)

In my Work Profile, I've got:
Version 124.0.6367.42.0

app.vanadium.webview
versionCode 636704233

targetSdk 34
minSdk 29

Installed: 27.03.2024; 22:31
Updated: 13.04.2024; 16:02

And in my main Profile:
Version 124.0.6367.42.0

app.vanadium.webview
versionCode 636704233

targetSdk 34
minSdk 29

Updated: 13.04.2024; 16:02

Seems like both are the current version, but I also can't uninstall updates: The button doesn't show up where I used to see it on other apps, just a greyed-out "deactivate" and "force end".

This appeared without me actively updating anything, I just saw the error (same as OP) on my main profile in the notifications.

Could you please lead me into the right direction?
Thank you!

@j6b72 You should be able to open the Vanadium System WebView-component via the "Apps"-app. (You might need to enable "show all apps" in the burger-menu)

From there you can open it's settings, where you can use the burger menu to "remove updates" or whatever it is called in your language. After that you can install the vanadium update after giving it a bit of time.

I have also disabled auto-updates for the work profile, it seems that was the initial problem. Hopefully this doesn't repeat

That worked, thank you!

Uninstall Webview Update from Work Profile, Update Vanadium from Main profile, Update Webview from Main Profile. Seems like everything's clean & updated.

Thanks!

@newhinton I removed updates for the work profile's Vanadium System WebView and still got an error message when I tried to update Vanadium on the main profile. I don't recall what the message was 2 days ago, but this is what it says today after my phone's been off for a few hours...

Installation failed
Unable to install Trichrome Library, Vanadium Config, Vanadium.

Details:
0

Pixel 6a
Android v14
main profile:

  • Vanadium v124.0.6367.54.0
  • Trichrome Library v124.0.6367.82.0
  • Vanadium Config v12
  • Vanadium System WebView v124.0.6367.54.0
  • Apps v22

@QuestioningEspecialy You haven't fully undone what you did.

@thestinger what in da hell...
pretty sure i pressed that remove button 2 days ago, but it was still there when i just checked
now my main profile's Vanadium (and then Vanadium System WebView) managed to update 🤷🏿‍♂️
thanks

Greetings, I'm having a similar issue, if not the same.

`Unable to install Vanadium Config, Vanadium, Trichrome Library, Vanadium System WebView: package conflicts with another package that is already installed on this device.

Details:
INSTALL_FAILED_DUPLICATE_PACKAGE: Packages declaring static-shared libs cannot be updated`

I read this thread and tried uninstalling updates for vanadium, vanadium config and vanadium system webview.
I tried updating from all profiles I use.
I still can't update.

Is there a chance that I can't update because I have so another chromium based browser? (Specifically chromite).

@moeraccoon No, as explained above, this is because you updated Vanadium browser or Vanadium WebView in a profile without updating the other and are now trying to update the other in a different profile. It has nothing to do with using another browser. Vanadium uses properly namespaced package ids starting with app.vanadium. and nothing else should be using that. You should update to Apps version 23 first which has a workaround for this Android usability issue via a new OS feature added by GrapheneOS.

Apologies and thank you, I thought that using update all would've worked the same, I didn't understand I had to update specifically apps alone first.

@moeraccoon It would have updated Apps first for automatic updates but for manual updates it doesn't do that. With the old Apps version, you would have had to work around this Android issue by updating Vanadium WebView in the same profile you updated Vanadium browser. We used to force them to be updated together but we split them apart since that works fine, which led to uncovering that there was an Android usability issue with shared library updates we had to work around.

Thank you very much for your help and your work friend :)