Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notify and resume of unsuccessful uploads #184

Open
Zvezdin opened this issue Feb 27, 2020 · 2 comments
Open

Notify and resume of unsuccessful uploads #184

Zvezdin opened this issue Feb 27, 2020 · 2 comments
Labels
type:feature-request New feature or request
Milestone

Comments

@Zvezdin
Copy link

Zvezdin commented Feb 27, 2020

Basic Info

Android 10 One UI 2.0
Galaxy S9
I'm running Cryptomator in version: 1.4.3

Description

When a multi-file upload process is started and left in background, it may be stopped by Android due to insufficient memory. In this case the user is never notified that the process actually did not complete successfully and some files are missing.

It would be nice to have a log and see which files were successfully and unsuccessfully uploaded, as well as have the option to resume unsuccessful uploads. Otherwise it is a significant hassle to go back and count all the files manually to ensure nothing is missed.

edit: This is another issue that I am having but not sure if it warrants a formal issue on its own. Almost all upload processes that I start (~10-50 images each) in the background do not finish, even if my device has 2GB free memory at the time. When I reopen the app the vault is still accessible and unlocked and it does not seem like the app has been killed. Is this a reported issue or is it likely due to something external consistently killing the upload process specifically?

@SailReal SailReal added the type:feature-request New feature or request label Mar 12, 2020
@SailReal SailReal added this to the Backlog milestone Mar 12, 2020
@SailReal
Copy link
Member

Thanks for the feature request 👍
We're currently focusing on other features e.g. finishing 1.5.0 but this will be implemented for sure!

@SailReal
Copy link
Member

SailReal commented Apr 7, 2020

Almost all upload processes that I start (~10-50 images each) in the background do not finish, even if my device has 2GB free memory at the time. When I reopen the app the vault is still accessible and unlocked and it does not seem like the app has been killed. Is this a reported issue or is it likely due to something external consistently killing the upload process specifically?

@Zvezdin I somehow missed the second part of your issue, we have to take a look at it. Can you please create a new issue with it and provide as many details as possible? App version, used cloud provider, occasional problem or does it always occur and send us a log when the upload is aborted after you activated the debug option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants