Using #FDroid Basic on #GrapheneOS. It looks like the recent #Android/GOS QPR3 updates broke F-Droid's ability to automatically update apps. Any info on that? @GrapheneOS @fdroidorg
@cryptgoat
Do you see the same with their "Apps" app? If so, it is an OS bug. Sounds like something in QPR3 has changed.
@grote Had no updates there since then.
@cryptgoat
By "broke ability to automatically update" you mean that you get a confirmation prompt? Does happen for all updates? Can you reproduce by installing old versions of apps? I sometimes get prompt and sometimes not. More likely to get prompt when trying to update right after install.
@cryptgoat You may just need to report it to Graphene once their own Apps app shows the same behavior. Calyx has a ticket here: https://gitlab.com/CalyxOS/calyxos/-/issues/2473 which shows stock Android is fine.
@grote Alright, thanks. #Obtainium appears to be affected too.
@cryptgoat Then it is most likely an OS issue in need of upstream reporting.
@grote
Well, Aurora Store and the GOS Apps app are still working fine.
@cryptgoat
Very strange.
@cryptgoat @grote same here.
@johanneskastl @cryptgoat On GrapheneOS and only F-Droid and Obtainium can no longer update apps they installed without prompt, but Apps and Aurora can?
@grote @cryptgoat GrapheneOS apps are auto-updating. I have not gotten missed updates in Aurora yet, so it seems auto-updating, too.
F-Droid notified me of updates that I had to install manually.
(No obtainium installed)
@johanneskastl @grote Installed the latest #GrapheneOS update: https://grapheneos.org/releases#2024062000
F-Droid updates are still borked.
@cryptgoat any chance you can capture a full logcat from the moment you press "update" in fdroid until the confirmation dialog appears? @johanneskastl
@grote Any recommendations to accomplish this? GrapheneOS allows you to capture app specific logs. @johanneskastl
@grote It's been a while since this started, but I had a look at it now and captured logs (https://gitlab.com/fdroid/fdroidclient/-/issues/2828#note_1997352220) from an app update via F-Droid.
The permission check (https://gitlab.com/fdroid/fdroidclient/-/blob/master/app/src/main/java/org/fdroid/fdroid/installer/ApkVerifier.java#L86) that F-Droid performs results in a mismatch as the actual set of permissions always contains 'OTHER_SENSORS' as an additional permission (https://grapheneos.org/features#sensors-permission-toggle).
As a consequence, F-Droid falls back to the default installer (https://gitlab.com/fdroid/fdroidclient/-/blob/master/app/src/main/java/org/fdroid/fdroid/installer/Installer.java#L322), which means an install dialog is shown.
@min7 Thanks, that's very helpful. It also explains why other apps and other ROMs are not affected.
@min7 unfortunately, the paste isn't found. Could you upload again, or add here: https://gitlab.com/fdroid/fdroidclient/-/issues/2828
Also, do all apps use that permission or just some based on other permissions? Is there a reliable of identifying GOS at runtime through a build prop for example?