We have vastly improved our cloud service implementation across our apps. You will need to enable your preferred service again. Please read Supported services and Common features for detailed information.
Our cloud service implementation is more than 4 years old and needed constant maintenance in order to keep-up with changes brought by different services.
We have decided to start from scratch and re-implement it as a maintainable, sustainable and expandable system. This makes it a lot easier to add new services or modify existing ones.
The way we implement Google Drive has changed significantly because Google is limiting 3rd party app access to Google Drive. Our apps only have access to folders and files they create. They cannot see folder or files created by you or other apps. This means you cannot set our apps to save to a sub folder you have created. Files are saved at the root of your Google Drive in a folder with same name as apps' package name. For example "com.nll.asr", "com.nll.acr".
Our apps only have access to their special "Apps" folder at the root of your OneDrive. You can use business or personal Microsoft accounts to connect to your business or personal OneDrive.
Our apps only have access to their special "Apps" folder at the root of your Dropbox.
Uploads are saved at the root of your Box account in a folder with same name as apps' package name if you do not define remote folder. For example "com.nll.asr", "com.nll.acr". Uploads are saved in to the remote folder if you do.
Our apps support the following services. iCloud/Me.com, Gmail, GMX, Hotmail/Outlook, Mail.ru, Yahoo, Yandex.
You can also use your own custom SMTP server. Just select Custom SMTP from the menu and add your server.
Some services might require App Passwords for sending email with 3rd party apps.
How to create Gmail/Google App Password
How to create Hotmail/Outlook App Password
How to create Office 365 App Password
How to create Yahoo App Password
How to create Yandex App Password
Custom FTP or FTPS servers fully supported
Currently only password authentication is supported. We hope to implement certificate authentication in the future.
We have couple of pre-defined popular service configurations under WebDAV Settings. Just select your favourite service from the list and enter your details to connect. Please note that self-signed SSL certificates are not supported at the moment. We hope to implement self-signed certificate support in the future.
A WebHook can be described as a web event. If you have your own web server and some development knowledge you can enable our apps to send requests to your server. It can be used to upload recordings or files. Self-signed SSL certificates are not supported at the moment. We hope to implement self-signed certificate support in the future.
Create a web page or service that accepts following form data and enter its URL to Server setting under WebHook settings. Our apps will post following multipart/form-data to the address you have provided.
Our apps expect response with HTTP status code 200 for successful upload/post. If status code returned is either 401 (unauthorized) or 404 (not found) they would automatically disconnect from the service unless Auto disconnect disabled.
See our repo at https://bitbucket.org/copluk/acr-webhook/ for open source implementations of front and backends. Please note that previous version of our cloud services used post more data and backend code in the repo configured accordingly. You might need to alter them according to new specification above.
This is not a cloud service in a traditional sense but a backup destination. You can select your SD card or any other folder on your device for our apps to export their files as scheduled.
You can see status of old or pending uploads per service, clear completed uploads or force uploading.
You can enable Upload Organiser per service. Upload Organiser creates folders on the cloud service according to your preference. For example, you can set organiser to create folders by "/Device name/Year/Month/Day/". This would allow you to upload from different devices separately.
Cloud Services now supports multi accounts per service. You can add multiple FTP, FTPS, SFTP, WebDAV, WebHook, Email and Device services. Some services such as Google Drive does not support multiple account.
Cloud Services can be set to upload only when there is an active Wi-Fi connection.
Unlike previous version, new Cloud services use schedules for uploading. Our apps schedule a onetime upload job to run in the next 30-60 seconds after you create a recording or file. There is also a periodic upload job that runs every 1-2 hours to process failed or pending uploads.
You can set file size limit per cloud service so that only files smaller than the set size are uploaded. Email services have pre-defined size limits according to email providers' limitations.
You can enable cloud delete per service so that our apps attempt to delete uploaded files when you delete it from the app. Cloud delete is a "lazy" operation. It might not work if you use Upload Organiser.
By default our apps will disconnect from the service if they detect an issue with service. You can disable this feature by service. This is especially useful when you are using a self-hosted service such as FTP that is not available on every network.
For example, imagine you have an FTP server at your home or office that is not accessible from the internet. Our app would attempt to upload when you create a recording or file while your FTP server is inaccessible and would not disconnect from the service if you have auto disconnect disabled.
You can manually re-schedule upload. Simply tap on a recording or file in our apps and select "Queue for upload". Please note that some services do not accept re-upload and you might get upload failed errors.