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
You should see the loading spinners immediately start loading from the cloud or very clearly indicate if that is what is happening, and ideally show which are already done.
Selection limit should be indicated in the UI somewhere, based on the customPickerOptions.maxFiles setting.
(note: this currently happens after you select files and then click "done" – it notifies you that not all were selected, but how do you go back to gallery and know which ones were not?)
Current Behavior
iOS
When you click on files that are stored in iCloud (which is almost all of them if you click the setting to "save space on your device") the file will show a white circle loading indicator in the center of the thumbnail, and then it goes away when done. If you upload more than a few files then this seems almost random and not sequential, and you do not see which are needed and which are completed. Especially if your initial selections are scrolled out of view.
Additionally, if you click "Add" again since you have no idea what is happening, the process restarts in a seemingly random order.
Android
This issue was deemed sufficient and not a blocker on Android, based on internal video upload testing.
Possible Solution
Keep the completed circle indicators on top of the thumbnail when they are done, or maybe show a thumbs-up?
Do not re-start if they click "Add" again, rather see if anything changed and continue.
Show the maxFiles limit in the UI somewhere to avoid losing files when you click "done." Can you alert on click if you're beyond the maxFiles?
Or, just an indicator that "clips are loading from the cloud - be patient"
Nice to have: Show the ones that have already been uploaded in prior sessions (we could pass an array of filenames to the picker if that would be helpful)
Expected Behavior
You should see the loading spinners immediately start loading from the cloud or very clearly indicate if that is what is happening, and ideally show which are already done.
Selection limit should be indicated in the UI somewhere, based on the
customPickerOptions.maxFiles
setting.(note: this currently happens after you select files and then click "done" – it notifies you that not all were selected, but how do you go back to gallery and know which ones were not?)
Current Behavior
iOS
When you click on files that are stored in iCloud (which is almost all of them if you click the setting to "save space on your device") the file will show a white circle loading indicator in the center of the thumbnail, and then it goes away when done. If you upload more than a few files then this seems almost random and not sequential, and you do not see which are needed and which are completed. Especially if your initial selections are scrolled out of view.
Additionally, if you click "Add" again since you have no idea what is happening, the process restarts in a seemingly random order.
Android
This issue was deemed sufficient and not a blocker on Android, based on internal video upload testing.
Possible Solution
Keep the completed circle indicators on top of the thumbnail when they are done, or maybe show a thumbs-up?
Do not re-start if they click "Add" again, rather see if anything changed and continue.
Show the
maxFiles
limit in the UI somewhere to avoid losing files when you click "done." Can you alert on click if you're beyond themaxFiles
?Or, just an indicator that "clips are loading from the cloud - be patient"
Nice to have: Show the ones that have already been uploaded in prior sessions (we could pass an array of filenames to the picker if that would be helpful)
Steps to Reproduce (for bugs)
"filestack-js": "^3.32.3"
Additional Screenshots
Upload 20Mbps, Ping 23ms, 300Mbps Download
Context
Beta users have complained about the upload experience - need help to resolve and make it production-ready - thanks!:)
Your Environment
"filestack-js": "^3.32.3"
The text was updated successfully, but these errors were encountered: