REGRESSION BUGS FOUND:
NOTE:
BRANDING CHANGES
1.- Set a txt file as "available offline"
2.- Enable the airplane mode in the device
3.- Modify the txt both in device and server
4.- Disable the airplane mode
5.- Pull down to refresh -> conflict is detected
6.- Change orientation of the device
Conflict is solved magically
Conflict remains until the user decides what to do, whatever action that he/she performs
Tested with HTC One v4.3, Samsung Galaxy Note4 v5
@jesmrec https://github.com/owncloud/android/issues/1686#issuecomment-222476227 Bug fixed :)
1.- Set a file as "available offline"
2.- Remove locally the file
File is locally removed. In this case, if the device lost the connection will not be downloaded and will not be available offline
File can not be locally deleted if it is "Available offline"
Tested with HTC One v4.3, Nexus5
1.- Set a file as "available offline"
2.- In server or in another client, rename the file
File is not available offline
File keeps on being available offline
Tested with Nexus7 v4.3, Nexus5 v5.0.1
1.- Share a folder by link
2.- Enable "Allow Editing" option
3.- Enable Password Protect/Expiration Date
"Allow Editing" is disabled. Any change in "Password Protect"/"Expiration Date" switch "Allow editing" if it is enabled.
"Allow editing" is enabled
File keeps on being available offline
Tested with Nexus7 v4.3, Nexus5 v5.0.1
Server v9.0.2
Are all these potential bug reports showstoppers for a minor bugfix release?
I mean people are waiting for bugfixing for some major errors that came with 2.0.0 and that broke some core features.
Instead of quickly hot fixing these new errors community makes a long term release for potential bug that are unclear to be one.
@johnripper1
The bugs that will be fixed in the new version are already fixed and validated. A new version always leads regression tests to assure the quality of the whole app to avoid new bug fixing versions. Anyway, the new version is close to be released.
@jesmrec , about "Renaming in server loses av offline" in https://github.com/owncloud/android/issues/1686#issuecomment-223941858 ; this is not a regression, I think we should open a new issue and deal with it in future releases.
@davivel. Opened in https://github.com/owncloud/android/issues/1703. Closed for the current version.
The other one https://github.com/owncloud/android/issues/1686#issuecomment-223948028 is not a regression either, but probably it's an easy fix. I'll have a look
@jesmrec ,https://github.com/owncloud/android/issues/1686#issuecomment-223948028 is fixed now in release_2.0.1.
Fixed the bug, and finished the validation
Dammit, changelog is not in place... :/
And now it's DONE
It' already in the Play Store. Updated already.
@all: Thank you very much, good Job!
Most helpful comment
It' already in the Play Store. Updated already.
@all: Thank you very much, good Job!