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
Version: 3.0.0-alpha.1
System: all desktop (on mobiles there is no downloading functionality yet)
Issue: when a new user joins a community in which bigger files have already been uploaded, this user doesn't have the option to download them (there is no "download" button). It's not a consistent behavior, but it appears frequently. It should be easy to reproduce.
Note - I add it to the current sprint but it's to be decided if we are fixing this now or in the future.
The text was updated successfully, but these errors were encountered:
While both are online send multiple files and images from one user to another, including at least 2 that are not auto downloaded
Start downloading one of the large files and then cancel the download
Create another peer and connect them to the community
What I saw was that the file I had not cancelled has no download button on the third peer but does appear on the file that was cancelled on the other peer.
Things I've noticed
I couldn't get this issue to show up before cancelling a download
Adding extra logs I see that the message shows up in the addMessagesSaga but not in the autoDownloadFilesSaga even though they both get triggered by the same events - they should get the same message IDs but the file with the missing button doesn't show up in the list of IDs sent to autoDownloadFilesSaga
Version: 3.0.0-alpha.1
System: all desktop (on mobiles there is no downloading functionality yet)
Issue: when a new user joins a community in which bigger files have already been uploaded, this user doesn't have the option to download them (there is no "download" button). It's not a consistent behavior, but it appears frequently. It should be easy to reproduce.
Note - I add it to the current sprint but it's to be decided if we are fixing this now or in the future.
The text was updated successfully, but these errors were encountered: