Google Play Store tries to update my F-Droid apps :-(

Thanks for the suggestion. This has fixed the problem to my satisfaction. Aurora Store is easy to set up and does a good job. I’ve stopped all notifications from Play Store so it can offer me updates to F-Droid apps for as long as it likes!

3 Likes

This is a workaround not a solution

The issue with the Play Store can only be solved by Google. That conversation must hence happen elsewhere.

This discussion here can only inform about the issue, help analyzing it and help with suggestions on how to deal with it.

1 Like

Sorry to say, wrong again…

This issue is not being resolved by Google as it is working as they intend.

So stuff Google and use Aurora Store. I’ve not had any problems since I changed, in fact I’m pleased Google introduced this “bug”, Aurora Store is a great discovery.

1 Like

Looks like you attached a different picture, one that is not related to this issue.

Can you reattach the one about F-Droid pls? You do have one, yes?

When you see this, please press the “Submit feedback” button from the error message (DO NOT SUBMIT A REVIEW OF THE APP ELSEWHERE) and tell them: “Google Play erroneusly tries to update an app signed by a different key” or “Play erroneously tries to update apps signed with a different signature from a different store” or something like this.

On Android 14 and later, there’s even a “Installed by” property per app, and, if you used Signal’s internal updater, that should say “Signal” and not “Play”.

no because my point is intent in the policy at Google and that would then be off topic of my response that what is marked as a solution is a workaround or an advertisement to lure users away from F-Droid.

I’ve un-marked the solution, as there is none (here).

1 Like

When you see this, please press the “Submit feedback” button from the error message (DO NOT SUBMIT A REVIEW OF THE APP ELSEWHERE) and tell them: “Google Play erroneusly tries to update an app signed by a different key” or “Play erroneously tries to update apps signed with a different signature from a different store” or something like this.

No because it is working as Google intends it to, perhaps instead provide instructions to report Google to the EU or Anti trust authorities in the US.

On Android 14 and later, there’s even a “Installed by” property per app, and, if you used Signal’s internal updater, that should say “Signal” and not “Play”.

Actually it is unclear what the intent Signal has remaining on the Google Play store, not having Signal available via F-droid, and very little information regarding this mysterious updating infrastructure you mentioned.

Big BTW Thank you soo much for your Contributions to open source Licaon_Kter

The current EU DMA process that investigates Google, Apple, etc, targets this too. No, it’s NOT working as Google says it should (if it’s working as they want is a different thing)

“Easy” to install, that’s why Quicksy exists and it’s free on Play too. So n00bs don’t need to “toggle unknown sources” or download random APKs…

old thing, that’s how they want it, also, in the current state with Google proprietary dependencies, it can’t just be added

Signal updates from their site. What do you mean?

thanks for zealoting! :smiley:

No Aurora Store will not work with all apps, trust me let me show you my work.

Absolutely not “wrong” (whatever that would even mean). Even if Google does not want to solve the issue, they are still the ones who would need to do so. You can complain all day long here on the forums that nobody provides a solution, but all that can be done is to provide workarounds.

1 Like

I’ve had no issues with any apps I run so I’m happy as, it seems, are most users.

Using Aurora Store and silencing Play Store doesn’t stop one firing up the latter occasionally and checking for missed updates. All I’ve found so far are apps installed from F-Droid which won’t install anyway.

If this behavior is actually Google policy then they’ve shot themselves in the foot.

2 Likes

good news: Request update ownership for newly installed apps (!1370) · Merge requests · F-Droid / Client · GitLab

of note, latest F-Droid Client 1.20-alpha1 has improved the triggers that help keep Play at bay and behaving.

Maybe you, and you and you :slight_smile: can update and test ?

4 Likes

Update installed. Looking for a negative result means it may be weeks before I can be sure it is working.

1 Like

Unfortunately the updated F-Droid has not helped. Google Play today wants to update Tutanota which I installed from F-Droid.

1 Like

That should not have happened. Very odd behaviour. Although Tutanota or other apps maybe available from PS probably too.

Did you read latest TWIF? Maintaining ownership | F-Droid - Free and Open Source Android App Repository

In short, Google’s defense is “only our Android, we don’t know what other OEMs do”

So, to be able to test this you need:

  • latest stock Android 14
  • a Google device
  • F-Droid Client 1.20-alpha1

When you have those (maybe have 14 on a non-Pixel, maybe that’s enough?) you INSTALL or UPDATE an app WITH 1.20-alpha1

And THEN only FOR THAT APP you test if Play wants to update it.

You can easily do that, expand Versions in Client, scroll to an older version for an app that’s in Play too and that you did not instals yet, eg. Quicksy 2.14.2

After that, wait… restart device… check updates screen in Play…whatever

I had not taken to heart that it only applies to Android 14 and over. I have only A11 on my phone.