Deutsch English Français Italiano |
<vdk5nh$nim$1@nnrp.usenet.blueworldhosting.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder8.news.weretis.net!npeer.as286.net!npeer-ng0.as286.net!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!feeder2.feed.ams11.usenet.farm!feed.usenet.farm!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail From: Andrew <andrew@spam.net> Newsgroups: comp.mobile.android Subject: Re: Paid apps Date: Wed, 2 Oct 2024 19:08:33 -0000 (UTC) Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com) Message-ID: <vdk5nh$nim$1@nnrp.usenet.blueworldhosting.com> References: <lm01tcFes3sU1@mid.individual.net> <ftnvskx2ho.ln2@Telcontar.valinor> <lm4s23F6khhU3@mid.individual.net> <v7svskx1l4.ln2@Telcontar.valinor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Wed, 2 Oct 2024 19:08:33 -0000 (UTC) Injection-Info: nnrp.usenet.blueworldhosting.com; logging-data="24150"; mail-complaints-to="usenet@blueworldhosting.com" User-Agent: PhoNews/3.13.3 (Android/13) Cancel-Lock: sha1:RCCA+1n2wAtKESPipIKrOuffdWM= sha256:zLJbkAhLURW8XO44X8gNsPKyucHtDdv3B1DAPKOspP0= sha1:Z/wtY8g88iDJvHhLii0uV0KIUQg= sha256:mkmcMOhr7Bfxgq6BontvC06C7kqV8vMVTbuc1hzHG7o= X-Received-Bytes: 2791 Bytes: 2955 Lines: 38 Carlos E.R. wrote on Wed, 2 Oct 2024 14:51:43 +0200 : > On 2024-10-02 14:19, Andy Burns wrote: >> Carlos E.R. wrote: >> >>> some of these apps have a free version in the Play Store, and some >>> times another one in F-Droid; but they are not the exact same one. >> >> I gather google is moving to enforce install of apps from the play store >> if you try to sideload them, or load them from alternate stores? > > Not exactly. What I read is that you can not install one way and update > the other. And developers can choose to block different install methods. The way it has been, for a while, but it has already changed a few times, is that if you load an app from location 1, it's signed with a certain signature which is different than if you loaded that same app from location 2. So if you loaded it from location 2, you have to update from location 2. Otherwise the signatures don't match. However... that's only the most simplistic view as Google recently allowed developers to share the credentials among locations, so anything can be the case for any given app. Safest way around all that complexity is to update from the same repository that you got your app from. I even have started inserting the repository name into the download of the APK (since I do all my Android APK installs from Windows). fdroid_name.of.apk github_name.of.apk google_name.of.apk Let's hope Google hasn't messed with this, as I don't even have the Google Play Store package installed on my non-rootable Android user partition. It's never needed.