we will soon be ready to have a new release finished up and ready to release. Since the Android Team is rather small we will not just ship stable releases but also make use of the beta program of the app store. So we will release a new version as a release candidate to the beta channel and leave it there for about two weeks monitoring any issues on the smaller user base and after that will release it as stable with bug fixes found during the beta time.
As for the f-droid users we do public beta releases that can be run in parallel and ship with many new features which might not be too stable but give you the opportunity to test out new stuff and provide us with valuable feedback and bug reports so we can polish features before shipping them to the masses.
So it will be released to the FDroid beta channel at the same time? Currently I have both beta and stable installed via FDroid, although beta crashes every 30 seconds or so (Samsung Galaxy Grand Prime). Iāll be curious to see if the new beta does the same thingā¦
@Bugsbane No it wonāt since the beta on f-droid is something different, we now work with three kinds of releases
stable: to be released to f-droid and Play store
beta: only released to f-droid and can be installed in parallel
release candidate: Play store beta release
If the app crashes directly during the start please open a new issue on the tracker. Are you running the latest beta release (Version 20160621)?
The ārealā beta thus doesnāt do the same thing since it is another app which ships with a bleeding edge code base. As soon as we are done with integrating most of the open but implemented features into the stable app we will most likely drop the f-droid beta app since it shouldnāt be needed anymore because we plan to ship in shorter cycles than we could with the oC app.
Sad to hear that youāll be dropping the FDroid beta, as I really wonāt be subscribing by the Play Store. I guess itāll need to be direct, manual downloads of APKās instead, then? Opening an issue on Github for the crash, nowā¦
No worries, itāll take some time until that happens and then there will only be a 2 week gap between release candidate and stable release. And they will have de facto feature parity.
Hi @Bugsbane good question
We havenāt thought about that scenario yet (f-droid users who would be willing to run release candidates). The unfortunate part why we havenāt included the release candidate process is because f-droid isnāt a fully blown app store but rather a apk directory. Publishing the APK within the Github repo might be an option though I need to discuss with @tobiasKaminsky and @LukasReschke. The downside is that you wounāt have any nice update mechanism
Regarding your reported issue, that one isnāt related to the backend.
Obviously, Iād rather have a nice update mechanism, however that said, Iād prefer manually installing APKās - wherever theyāre stored - over not being able to help with testing, or having to go through the Play Store. Obviously, Iām assuming that any APKās would be somewhere secure with at least SSL and checksums.
Will upload all builds uploaded to the Playstore also to https://download.nextcloud.com/android/ then. They will have the same signatures and checksums like the server releases then.
@Fred_Dresken_Maveric most likely not f-droid does its own builds so it wonāt be signed by Nextclouds keystore thus security will prevent the update. But since you already signed up to the beta program on Google play you can simply reinstall from there. Sorry for the inconvenience.
we just pushed the first release candidate of the upcoming release 1.1.0 to the Google Playās beta channel so it should show up within the next hours. For everyone who isnāt using Google Play we provide the APK files via https://download.nextcloud.com/android/
The new release brings you the following features:
New main menu to switch accounts easily
Ability to open Nextcloud hosted files (read-only) from other apps that support the standard file chooser (requires Android 4.4 / KitKat or higher)
āSelect all filesā for upload within a folder
optional feature to auto-create monthly folders for your instant uploads
we just pushed the first release candidate of the upcoming release 1.2.0 to the Google Playās beta channel so it should show up within the next hours. For everyone who isnāt using Google Play we provide the APK files via Index of /android
The new release brings you the following features:
Multi select capabilities
confirmation dialog on account removal
offline available filter in main menu
sorting capability when choosing files to be uploaded
video thumbnails if activated on server
thumbnails during upload
fixed user agent for file firewalling
showing server side folder sizes
text in test preview can now be selected
search suggestions fixed for user/group search during sharing
A suggestion maybe covering this scenario: what about publishing to fdroid but not bumping the recommended version? The fdroid app developers do this all the time. Right now the newest fdroid release is 0.101-alpha2 but the default version which gets installed and which you get update notifications about is 0.100.1.
As far as I understand: we only have to add the RC as a new build to metadata, but not change the current version?
But how to do that as the build infos are auto generated via
We would have SSL while having the APK in the repo. We wonāt have checksum out of the box there.
--> 
