From eb46ff0eef573aa635c1afdf4abd5409033150bd Mon Sep 17 00:00:00 2001 From: M66B Date: Sun, 4 Feb 2024 11:20:33 +0100 Subject: [PATCH] Updated FAQ --- FAQ.md | 4 ++++ index.html | 1 + 2 files changed, 5 insertions(+) diff --git a/FAQ.md b/FAQ.md index 8b6c7dac96..76bc62dfa2 100644 --- a/FAQ.md +++ b/FAQ.md @@ -4476,6 +4476,10 @@ which mostly involves signing a contract with binding terms and conditions. Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install ("*App was not installed*") the same app with a different signature for security reasons. +At the start of 2024, the Play Store app started to update all apps, including apps not installed via the Play Store. +Since the F-Droid build is signed by the F-Droid organization, which basically means the F-Droid build is another app, updating the F-Droid build will fail. +Unfortunately, there is no way to resolve this. + Note that the GitHub version will automatically check for updates. When desired, this can be turned off in the miscellaneous settings. diff --git a/index.html b/index.html index c9f3591ba3..9e7766aa6e 100644 --- a/index.html +++ b/index.html @@ -2229,6 +2229,7 @@ $NotDisplayed

F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.

OAuth access is available only for Play Store and Github releases because email providers permitted the use of OAuth for these releases only. The responsible for a release, for the F-Droid build this is the F-Droid organization, needs to ask for OAuth permissions, which mostly involves signing a contract with binding terms and conditions.

Note that you’ll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install (“App was not installed”) the same app with a different signature for security reasons.

+

At the start of 2024, the Play Store app started to update all apps, including apps not installed via the Play Store. Since the F-Droid build is signed by the F-Droid organization, which basically means the F-Droid build is another app, updating the F-Droid build will fail. Unfortunately, there is no way to resolve this.

Note that the GitHub version will automatically check for updates. When desired, this can be turned off in the miscellaneous settings.

Please see here for all download option and see here for the differences between the different release types.

If you have a problem with the F-Droid build, please check if there is a newer GitHub version first.