-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gplay release outdated (3.29.2 instead of 3.30.3) #13871
Comments
There does seem to be something off. We've received just two We can't use 3.29.x to directly compare (since it was never published on F-Droid), but the Incomplete, but the data is suggestive (and compelling).
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. 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. |
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?
The text was updated successfully, but these errors were encountered: