Private links generated by the server, must be opened inside the oC Android app.

This is a first approach with specific ACs:

• App matching the host to be opened when private link is clicked. Not needed to brand this. Static.
• Working in only one account mode
• If the link points to a file, the file will be downloaded/displayed
• If the link points to a folder, the folder content will be displayed
• If a locking method is set up, the file/folder will be displayed after unlocking
• If device does not have connection but the file is already downloaded, file is displayed
• If device does not have connection but the folder is already discovered, content is displayed
• If the file/folder is not reachable, app is opened and error is shown (toast/snackbar/...)
• If no accounts are attached in the app, app is opened and error is shown (toast/snackbar/...) (feasible?)

Additional checks:

• Lack of URL in the scheme (or *) are valid as well.

TASKS

• Research (if needed)
• Create branch feature/deep_links
• Development tasks
  • Implement intent-filter and launch it throught adb's command.
  • App matching the host to be opened when private link is clicked. Not needed to brand this. Static.
  • If no accounts are attached in the app, app is opened and error is shown in toast
  • If the file/folder is not reachable, app is opened and error is shown (toast/snackbar/...)
  • If a locking method is set up, the file/folder will be displayed after unlocking
  • Working in only one account mode
  • If device does not have connection but the folder is already discovered, content is displayed
  • Lack of URL in the scheme (or *) are valid as well.
  • If the link points to a folder, the folder content will be displayed
  • If the link points to a file, the file will be downloaded/displayed
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch feature/feature_name into master

PR

• App Open deep links in app, items already discovered (1st round) #3598
• Library (if needed)