You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before: App is locked immediately when user selects a locking method (passcode/pattern/biometrical)
2.20: User can set a delay, so that the app will not be locked till this time passes. It is useful if user works together with other app. Every time app is switched, passcode/pattern is skipped during the chosen gap time:
Enhancement - Lock access from document provider preference: #3520
Before: If the ownCloud app is locked with pattern lock or passcode, access to document provider was forbidden.
2.20: new security setting that let users decide whether the document provider access to the ownCloud files and folders is locked, regardless the locking methods.
Before : Security is optional, users decide by themselves whether they want to lock the app or not
2.20: New branding option, so, the app will be always locked using pattern/passcode when the option is true. This feature will not be available for Google Play users, only for customers (ownBrander and future MDM). That means, the "Before" scenario will be the same for those users in 2.20.
Enhancement - Respect capability for Avatar support: #3438
Before: User avatar always shown
2.20: Supporting new server capability to show/hide avatars depending on its value
Before: Users could try as many attempts as they want to enter a correct passcode.
2.20: Users have 3 attempts. After that, every attempt is only posible after waiting an increasing amount of time.
Enhancement - "Open with" action now allows editing: #3475
Before: The Open with action in the file list opens the file with external app but not posible to save changes back to the server.
2.20: The Open with action in the file list opens the file with external app and sync the changes back to the server. It will help users to edit files that are enclosed inside the scoped storage.
Enhancement - Biometrical protection enabled just after passcode/pattern: #3539
Before: Pattern/Passcode were enabled first, and then, biometrical protection in Settings in a different step
2.20: After entering correct passcode/pattern, a dialog will ask the user if he/she wants to additionally enable the biometrical lock:
Enhancement - Logs enabled by default in debug variant: #3526
Before: Logging feature disabled by default. User must enable it manually.
2.20: Logging feature is enabled by default if the app is built with debug variant.
Let me (or anyone in the team) know any question, issue or comment about this stuff.
The text was updated successfully, but these errors were encountered:
Features to include in the release. You can find the changelog here
I will briefly comment the enhancements. I guess bugfixes does not have nothing to do with documentation (let me know if i'm wrong)
Enhancement - Lock delay for app: #3344
Before: App is locked immediately when user selects a locking method (passcode/pattern/biometrical)
2.20: User can set a delay, so that the app will not be locked till this time passes. It is useful if user works together with other app. Every time app is switched, passcode/pattern is skipped during the chosen gap time:
Enhancement - Lock access from document provider preference: #3520
Before: If the ownCloud app is locked with pattern lock or passcode, access to document provider was forbidden.
2.20: new security setting that let users decide whether the document provider access to the ownCloud files and folders is locked, regardless the locking methods.
Enhancement - Security enforced: #3434
Before : Security is optional, users decide by themselves whether they want to lock the app or not
2.20: New branding option, so, the app will be always locked using pattern/passcode when the option is
true
. This feature will not be available for Google Play users, only for customers (ownBrander and future MDM). That means, the "Before" scenario will be the same for those users in 2.20.Enhancement - Respect capability for Avatar support: #3438
Before: User avatar always shown
2.20: Supporting new server capability to show/hide avatars depending on its value
Enhancement - Brute force protection: #3320
Before: Users could try as many attempts as they want to enter a correct passcode.
2.20: Users have 3 attempts. After that, every attempt is only posible after waiting an increasing amount of time.
Enhancement - "Open with" action now allows editing: #3475
Before: The
Open with
action in the file list opens the file with external app but not posible to save changes back to the server.2.20: The
Open with
action in the file list opens the file with external app and sync the changes back to the server. It will help users to edit files that are enclosed inside the scoped storage.Enhancement - Biometrical protection enabled just after passcode/pattern: #3539
Before: Pattern/Passcode were enabled first, and then, biometrical protection in Settings in a different step
2.20: After entering correct passcode/pattern, a dialog will ask the user if he/she wants to additionally enable the biometrical lock:
Enhancement - Logs enabled by default in debug variant: #3526
Before: Logging feature disabled by default. User must enable it manually.
2.20: Logging feature is enabled by default if the app is built with debug variant.
Let me (or anyone in the team) know any question, issue or comment about this stuff.
The text was updated successfully, but these errors were encountered: