Gilbert Gilb's b2ace0878c bring back upstream code for release APK check ... Upstream code checks whether the current APK was signed with the release key for various reasons: - in order to show/hide the "Updates" settings menu - in order to make the "Updates" settings menu searchable or not - in order to check/not check for updates at the application start This behavior was removed in NewPipe SponsorBlock fork, but it probably shouldn't have been: - the newer APK installation won't work if the locally installed APK wasn't signed with the same key - `isReleaseApk` function was still invoked in NewPipe SponsorBlock to allow searching "Updates" settings from settings menu. But as the fingerprint wasn't correct (see 25575ea8b2), the update settings would not be searchable which is a bug - this is a requirement for F-Droid inclusion as they sign their APKs with their own keys (so the updater wouldn't work) and they explicitly forbid auto-updaters by policy (see also https://github.com/polymorphicshade/NewPipe/issues/8)		2022-05-01 08:33:31 +02:00
..
schemas/org.schabi.newpipe.database.AppDatabase	Migrate NotificationIcon to Picasso	2021-09-07 13:30:26 +03:00
src	bring back upstream code for release APK check	2022-05-01 08:33:31 +02:00
build.gradle	Merge branch 'master' into sponsorblock	2022-04-30 12:19:11 -06:00
proguard-rules.pro	Fix proguard rules to keep Notifications settings fragment	2022-04-16 21:26:25 +02:00