-
Notifications
You must be signed in to change notification settings - Fork 153
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
Photos auto upload, final video upload task is copied multiple times #359
Comments
Hello alperozcetin, |
Hello @henry9610, Thanks, yes it seems this issue is resolved. However, I'm having another issue. I'm syncing ~5000 files to a new library, the app crashed several times during the process and at some point it was not possible to restart the app, it's being shutdown as soon as I start the app. I have restarted the phone, then app started to work again, but still occasionally failing. I'm also not sure what happens to the in-progress uploads when app crashes. Do they persisted to the server in a corrupt form, or somehow purged? Thanks |
Hi @alperozcetin , Thank you for bringing up this issue. I’ll try to reproduce it and investigate the cause. Additionally, could you please provide some more details, such as the iOS version, the app version, and whether there were any large file transfers involved? The issue you mentioned about how the server handles incomplete files during an upload interruption: the server does not retain incomplete files. Even if it does, they will be periodically cleaned up later. If the app is unable to start consistently, you can temporarily resolve the issue by uninstalling and reinstalling the app. I will investigate and address the problem as soon as possible. |
When there is only 1 video left in upload queue, and if it's size is big (5gb+), the upload task is copied multiple times. The same file is uploaded multiple times at the same time. Before 1 of those uploads finish, new tasks are created (for the upload of the same file) leading to slowdown of the app and unsuccessful upload.
The text was updated successfully, but these errors were encountered: