we are happy to announce the first release candidate for the upcoming Android release. It has already been published to the Play store and is also available for download at https://download.nextcloud.com/android/
As for the f-droid RC release, we are working on that.
Features you will get with this release are:
Files drop permission in share view
Display quota if configured/available in navigation drawer
Resume chunked uploads instead of complete restarts
Indeed back in my owncloud days I was using Synchronize Ultimate to do the job, mostly because I didnāt want to buy the app (I did eventually) but also because I wanted more than instant upload for the camera alone.
I may switch back to that until the NC client can auto upload from any folder as apps like Google Photos can currently. I know itās in the pipeline so look forward to seeing it work.
@guddl and @JasonBayton unfortunately the Android N instant upload issue still remains with 1.3 but @tobiasKaminsky and I want to takle it with 1.4, working on resolving this matter at the Nextcloud conference. Besides that I am also an Android N user since Preview 1 so I feel your pain since May
we are happy to announce the second release candidate for the upcoming Android release. It has already been published to the Play store and is also available for download at https://download.nextcloud.com/android/
As for the f-droid RC release, it might be available within the next 48h hours.
Features you will get with this release are:
Files drop permission in share view
Display quota if configured/available in navigation drawer
Resume chunked uploads instead of complete restarts
Filter remote and local file lists
Simple integration with DAVdroid for calendar and contacts sync (new in RC2)
TLS as SSL is a general characteristic of all client-server communication and as for TLS1.2 also depending on the ciphers hasnāt gotten any updates app-wise. This is an issue that needs a lot of testing and with the actual implementation we are bound to a very old http-client implementation (commons-httpclient-3.1) and I already opened up an issue https://github.com/nextcloud/android-library/issues/17 to replace this client library which might solve the TLS issue you mentioned by using httpclient-android-4.3.5.1 or even httpclient-android-4.4.1.1 mentioned in the issue. As I said this needs much testing and at the moment further investigation and try-outs to see if and how this impacts the implementation. I discussed the compatibility with the 4.4.1.1 author https://github.com/smarek/httpclient-android/issues/12#issuecomment-246116830 and one thing we would have to do to use this lib would be (at least a slight) refactoring/rewrite of our actual client implementation.
Will have to discuss the details on how to progress here with @tobiasKaminsky and may also @LukasReschke regarding security aspects but if you or anyone is is willing to jump in and help us with the implementation you, she or he is more than welcome
One other thing, just asking. @Guillaume would you be willing to provide a test account an a server with the mentioned TLS1.2 issue? That would help us a lot since I can only test any implementations against my own server (not having TLS1.2) and we are also relying on the reports we get from the beta app and the release candidates.
I am currently running 2 server for test purpose, one with NC 9 and one with NC 10.
Both are ubuntu 16.04 with NGINX and MariaDB. You can contact me by private message for accessā¦
Iām getting a minor issue where often when the app is loading the contents of a large direcory, it will say āloadingā¦ā and then āNo contents foundā only to then show the contents of the folder a few seconds later. Not sure if this is expected behaviour or notā¦
Oh, something else that I was also running into, but Iām assuming is my Nginx setup - not the Android app - is that files over 1gb seem to fail when uploading. Even so, if possible it would be nice to let the user know why uploads failed.
I did some update and testing since last day and found that in fact TLSv1.2 is working, depending of the cipersuite selected.
However, the Mozilla recommended choice is not working, and it is necessary to add (probably) weaker suite.
This is a bit confusing because the MacOS client is not working with TLSv1.2ā¦ It would be nice if it was the same configuration for all client (probably a Nextcloud decision)ā¦