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

Error page even after clearing cache in one browser #24245

Closed
non-Jedi opened this issue Jan 18, 2023 · 6 comments
Closed

Error page even after clearing cache in one browser #24245

non-Jedi opened this issue Jan 18, 2023 · 6 comments
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@non-Jedi
Copy link

Steps to reproduce

  1. Open https://develop.element.io in qutebrowser on one specific computer.
  2. "Something went wrong" error page.
  3. Click "Clear cache and reload"
  4. "Something went wrong error page"
  5. Clear site data from developer tools.
  6. Log back into my account on https://matrix.thebeckmeyers.xyz
  7. "Something went wrong error page"

Outcome

What did you expect?

To be able to use Element from the browser on this computer (everything works fine on other computers)

What happened instead?

"Something went wrong error page"

Operating system

Void Linux

Browser information

qutebrowser v2.5.2; Backend: QtWebEngine 5.15.2, based on Chromium 87.0.4280.144; Qt: 5.15.7 (compiled 5.15.5)

URL for webapp

develop.element.io

Application version

No response

Homeserver

matrix.thebeckmeyers.xyz (synapse 1.75.0)

Will you send logs?

Yes

@DrZingo
Copy link

DrZingo commented Jan 18, 2023

Same thing here, with almost the same setup. I can also confirm that it worked yesterday on this exact computer/setup.

Steps:
app.element.io
cleared cache with button on page - same issue.
cleared cache, cookies etc from developer tools - still the same.

Browser info:
qutebrowser v2.5.2
QtWebEngine 5.15.3
Qt: 5.15.6

Operating system:
Alpine 3.17

@qvatch
Copy link

qvatch commented Jan 18, 2023

getting this in windows 10 now, web app version, as a seeming result of hitting the update popup.

Steps:

  1. already logged in to app.element.io
  2. Click to upgrade
  3. "Something went wrong" error page.
  4. cleared cache with button on page - same issue.
  5. Tried hard reload (ctrl-shift-r) - same issue.

  1. Logged out of web app on desktop. Cleared site data from location bar, lock icon, 'clear cookies and site data'.
  2. Logged back in, verified with key.
  3. No error, but room list and conversations do not appear.
  4. Click on 'start conversation', select contact (the list is populated)
  5. "Something went wrong" error page.

  1. Try logging in with a different firefox profile that hasn't been used with element web in a while. Log in via github as before.
  2. Select verify with another device.
  3. Accept prompt on element desktop (1.11.17, olm 3.2.12) on the same computer.
  4. Compare unique emoji, select start
  5. Modal with "verify other device" and a spinner sits indef. (left 5 min, then cancelled)
  6. Try verify again, with iOS: element 1.8.12, sdk 0.23.2, olm 3.2.5, select no camera on device.
  7. Modal with "verify other device"
  8. select "can't scan"
  9. Spinner spins indef (left 5 min, then cancelled)
  10. Goto 16
  11. select "scan with this device"
  12. ipad gets camera view opened, webapp on windows remains unchanged at "verify other device/ To proceed, please accept.."
  13. Goto 16
  14. Try with android (element 1.5.11, olm 3.2.12), both options, same results as with ipad.
  15. Try 'start a conversation', as per step9, "something went wrong" error page.

Web app Element version: 1.11.18, Olm version: 3.2.12 [these are the numbers shown in settings>help/about on the window that is showing the error page]

Homeserver: https://matrix-client.matrix.org

Browser info:
Firefox 89.0.1

OS:
Windows 10 Pro, v2004, build 19041.508, feature 120.2212.31.0

Logs submitted prior to relogging (before step6).

Sorry for all the edits to add.

@uhoreg
Copy link
Member

uhoreg commented Jan 18, 2023

There is a known issue with the latest version and certain browsers. The team is working on a fix.

From the Element announcements room:

NOTE NOTE NOTE: this release has a known problem in browsers supporting older web standards. We are working on a fix now.

@uhoreg uhoreg added S-Critical Prevents work, causes data loss and/or has no workaround O-Occasional Affects or can be seen by some users regularly or most users rarely labels Jan 18, 2023
@uhoreg
Copy link
Member

uhoreg commented Jan 18, 2023

This should be fixed in the latest release (1.11.19). Can you try again?

@andybalaam
Copy link
Member

Huge apologies from all of the team for letting this issue slip through.

Fixed in v1.11.19

@non-Jedi
Copy link
Author

Can confirm that this is fixed on develop.element.io. Apologies for not reporting this issue sooner; I've been having it for several days. Might have avoided it making its way into a release if I had taken the time to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Development

No branches or pull requests

5 participants