gplay release outdated (3.29.2 instead of 3.30.3)

Latest nextcloud gplay release is 23.29.2 (https://play.google.com/store/apps/details?id=com.nextcloud.client):

F-Droid offers version 3.30.0 and github indicates version 3.30.3 as latest.

Is it a bug that those newer releases are missing in gplay app store or is it done by intention?

@AndyScherzinger

There does seem to be something off. We've received just two gplay edition crash Issues bug reports (of the auto-report variety) that are 3.30.x related (in comparison to eighty-five for generic). And we've had zero with 3.30.1 (but fifteen for generic).

We can't use 3.29.x to directly compare (since it was never published on F-Droid), but the gplay edition did receive 87 crash Issue auto-reports (some of which may even be because of availability...)

Incomplete, but the data is suggestive (and compelling).

e.g. 3.30.0
- gplay: 2 [direct installs maybe?]
- generic: 70
- https://github.com/nextcloud/android/issues?q=is%3Aissue%20state%3Aclosed%2030300090%20gplay

Cc: @AndyScherzinger, @ZetaTom, @tobiasKaminsky

One potential upside is... It means fewer end-users were impacted by #13738 (which is not the point, but still noteworthy).

I have the same problem. I would use F-Droid as the source, but then the notifications no longer work, right?

As of yesterday the latest release is 3.30.4 (https://github.com/nextcloud/android/releases/tag/stable-3.30.4) but the Google Play Store still offers 3.29.2.

I'm actually looking forward to 3.30.x because of the sync improvements, any chance the release to Google Play Store can be tracked somewhere? I know it can take some time to happen, but it'd be nice to know that it's happening.

Thanks!

Noticed this issue too today. Any ETA on this?

Google review is blocking us currently because we use the MANAGE_EXTERNAL_STORAGE permission, which was granted to us in early 2022, when it was introduced.
But suddenly they are not allowing us to use it.

Removing this permission would change auto upload behaviour quite a lot and thus I am in discussions with them, to keep this permission.

I will keep you updated.

@tobiasKaminsky

@tobiasKaminsky Any new information regarding this topic? 🙂

Google review is blocking us currently because we use the MANAGE_EXTERNAL_STORAGE permission, which was granted to us in early 2022, when it was introduced. But suddenly they are not allowing us to use it.

Removing this permission would change auto upload behaviour quite a lot and thus I am in discussions with them, to keep this permission.

I will keep you updated.

Are you guys just accepting this? I just filed a complaint with the european commission and the german Bundeskartellamt.

This is screaming conflict of interest like nothing else.

Are you guys just accepting this?

We are appealing since July but keep facing rejections on the appeals

And yes, this is screaming conflict of interest like nothing else - I think so too. However not being able to ship any updated at all thanks to their "policy" is also an issue and yes, to much power given to single platforms.

Do they state the reason why the permission declaration gets denied?

Also this issue is technically closed since an update has shipped thanks to #14099, but it night be nice to track the status of the appeal here? Or should a dedicated issue be created?

I thought about asking this in the pull request, but that feels wrong as well, so I am posting here:

Is there a suggested workaround for this issue?
For the average user that downloads an app via gplay and forgets about it, it might be best to inform them and say "sorry, there's nothing we can do about. It's Google's fault."

But since this effectively removes functionality it might be nice to have an alternative.
Couldn't a more tech-savvy user switch to the F-Droid release? Is this possible without losing data? Are there steps that need to be taken into consideration (e.g., somehow backing up and restoring the configuration for auto upload folders when switching app versions)?

I wonder why you aren't allowed to have the permission anymore.
Their documentation states thats your (our) usecase is okay: https://developer.android.com/training/data-storage/manage-all-files
(Hopefully this is the correct doc, I'm curious about the 'training' in the path)

If Nextcloud is open source and the community is expected to assist with development, bugs, maintaining various apps, the community needs some transparency on what Googles reasons are for declining so developers can work within Googles rules.

If Googles own rules or decisions maybe breaking some laws or regulations people need that info to be able to report them to the relevant authority.

Is there at least a way to receive push notifications when you install the app via F-Droid?

@strugee

Couldn't a more tech-savvy user switch to the F-Droid release? Is this possible without losing data?

You can't, because the F-Droid release is signed with a different key than the Google Play version. You have to completely uninstall and reinstall the app. You could try to back up your data beforehand with adb backup, but YMMV because that command is deprecated.

However! The APK in GitHub releases is signed with the same key as the Google Play version. So you could switch to that and use Obtanium to keep it up to date automatically.

Hey @strugee, just to clear it up for me and probably other users. Does the GitHub version still have the permission?

I've been using this one for a while, but the changelog seems to mean the permission is removed as well.

Your last paragraph however makes me think it is okay to install?

@tobiasKaminsky

@tobiasKaminsky might be able to give some more details on Google's rejections but to my knowledge Google doesn't provide a justification at all, they just state that you violate their rules (in this case making use of the permission in general).

This permission is forbidden to be used since 2022 except you were able to make a case on why you still need this permission, which we did back then. In July 2024 Google changed their mind and rejected any app update to the store until we remove the permission. We made appeals to them various times July till December. And to be clear we also stated that they themselves as well as competitors still use this permission hence we should be allowed too did help but got the reply: "Just because others still have the permission doesn't make your case valid...".

So after 4 months of no ability to publish an app updates to the store we gave in and removed the permission. So if anybody has any ideas or maybe contacts at Google to have a better way to get this address beyond reporting it to authorities, happy to pursue them.

@salixor

I've been using this one for a while, but the changelog seems to mean the permission is removed as well.

@salixor yes, has also been removed on the GH version, else we would need to maintain and publish yet another build flavor which is why we decided against it, but are willing to reconsider in the light of the discussion while to me this is merely a workaround adding extra work but not solving the situation for GPlay users.

Is it just me, or is this issue resolved already?

Yes, the new version 3.30.6 is already available via GPlay, however there are 2 issues (both already have Issue opened here):

It doesn't automatically request the new Media permission, so auto-upload just stops to work (you need to go to Auto-upload settings and only then it will ask for the permission)
It doesn't have MEDIA_LOCATION permission, so all uploaded media files will be silently stripped off all GPS metadata by Android system.

It doesn't have MEDIA_LOCATION permission, so all uploaded media files will be silently stripped off all GPS metadata by Android system.

That is a big problem.
Can it be fixed? Otherwise it makes the whole platform unusable for me

It doesn't have MEDIA_LOCATION permission, so all uploaded media files will be silently stripped off all GPS metadata by Android system.

That is a big problem. Can it be fixed? Otherwise it makes the whole platform unusable for me

Yes, there is already a PR: #14247

Title says gplay release outdated, it seems to me that has been fixed, let's not digress further

@XueSheng-GIT

Title says gplay release outdated, it seems to me that has been fixed, let's not digress further

Close this issue then?

cc @XueSheng-GIT

Close this issue then?

Yes, and I think it should be a unilateral decision by the maintainers:

There is no specific impact to begin with, only a question if the different versions on github and play store is intentional or a bug
And there is no clear answer if this is correct or incorrect behavior
But the version on play is now 3.30.7 and latest release on this repo is 3.30.7

@bilogic

Closing based on @bilogic reasoning.

Feel free to reopen if the specific issue is unresolved.

Navigation Menu

Repository navigation

gplay release outdated (3.29.2 instead of 3.30.3) #13871

2 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

gplay release outdated (3.29.2 instead of 3.30.3) #13871

Description

Activity

joshtrichards commented on Oct 26, 2024

Markoise commented on Oct 29, 2024

cmrtdev commented on Nov 1, 2024

MystikReasons commented on Nov 2, 2024

tobiasKaminsky commented on Nov 4, 2024

MystikReasons commented on Nov 14, 2024

chrissi5120 commented on Dec 9, 2024

AndyScherzinger commented on Dec 9, 2024

MrRinkana commented on Dec 16, 2024

shaaati commented on Dec 16, 2024

mieseprem commented on Dec 17, 2024

2 remaining items

sol8712 commented on Dec 26, 2024

Markoise commented on Dec 27, 2024

salixor commented on Dec 29, 2024

AndyScherzinger commented on Dec 29, 2024

AndyScherzinger commented on Dec 29, 2024

enoch85 commented on Dec 29, 2024

marki555 commented on Dec 31, 2024

Markoise commented on Jan 1, 2025

BluePixel4k commented on Jan 1, 2025

bilogic commented on Jan 14, 2025

enoch85 commented on Jan 14, 2025

bilogic commented on Jan 15, 2025

enoch85 commented on Jan 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions