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

Can't export app's cache/storage when Homeserver is destroyed #25988

Closed
AnotherNeko opened this issue Aug 17, 2023 · 1 comment · Fixed by matrix-org/matrix-react-sdk#11426
Closed
Assignees
Labels
A-Export-Chat O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@AnotherNeko
Copy link

Steps to reproduce

  1. Where are you starting? What can you see?
    Login to any account on any homeserver. Load an encrypted room (e.g. DMs) with some messages on the client. Then either turn off the network on the client computer or the homeserver (in my case, the network failed on the homeserver because the entire computer died.)
  2. What do you click?
    Room info > Export Chat > (HTML, Current Timeline, 99MB, Include Attachments)

Outcome

What did you expect?

Download a file containing all of the information the app currently has cached (I think that's what Current Timeline is supposed to do), without asking the homeserver for additional data.

What happened instead?

"Starting export…" spinner spins forever.

Operating system

Ubuntu (KDE Plasma Desktop)

Browser information

Firefox 116.0.1 (64-bit)

URL for webapp

https://app.element.io/#/room/!ulBgifyqVLmEcgHyLE:cocamserverguild.com

Application version

Element version: 1.11.39 Olm version: 3.2.14

Homeserver

dead server cocamserverguild.com

Will you send logs?

No

@AnotherNeko
Copy link
Author

the owner of the homeserver reset the entire system and now I've been automatically signed out and I can't access any of the cache that I used to have access to.

@dbkr dbkr added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow A-Export-Chat labels Aug 18, 2023
@t3chguy t3chguy self-assigned this Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Export-Chat O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants