Unconsistent history between browsers
What's happening?
On firefox, I cannot find some messages I posted a few minutes ago. Reload does not fix it. On chrome, logging-in with the same user and I can see them.
Steps to reproduce
Not sure about the reproduction steps though. Look inconsistent. It's sad :-(
Relevant logs and/or screenshots
Associated chrome and firefox screenshots:
As you can see there are additional messages on Chrome compared to Firefox. Seems that Matthieu received them actually so I guess they are actually present in the history.
Your Environment
I experienced that on https://community.startinblox.com, SIB-Core channel.
- Browser name and version: Firefox version 75.0
- Operating System and version (desktop or mobile):
- Ubuntu Desktop 18.10
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Link issues together to show that they're related. Learn more.
Activity
thanks for the issue @balessan !
@jbpasquier if we can reproduce it I think this is a bug we need to have a closer look. I'm unable to reproduce it so maybe we need to play with Benoit's account? Which team would we need to put on this?
- Owner
@balessan To ensure the steps you did:
- You started Firefox, sent a message and never saw it. Even if you refreshed the page. For notice, refresh will use cache, only a logout/login could reload your messages.
- You started Chrome, your message were here.
Right?
If so, I think it's on @deleolajide hands. :)
- Author Owner
@jbpasquier : I think I did the following:
- I posted them on Firefox,
- I should have closed the tab
- Reopened the app in another tab
- Message disappeared
- Open in Chrome/fresh start/login
- Message is here
- Today in Firefox message came back, so cache issue then ?
Edited by Benoit Alessandroni - Owner
Thanks!
Sounds like a cache issue, for sure, assigning @deleolajide so.
@rachel If you can add a priority tag on this, thanks!
I believe this is a severity 2 as not all our users will think about trying a different browser. So as soon as @deleolajide is finished with his current work, it could be nice to have him taking a look at this one.
- Please register or sign in to reply
- Jean-Baptiste Pasquier assigned to @deleolajide
assigned to @deleolajide
- Rachel changed milestone to %Chat (not in dedicated repo)
changed milestone to %Chat (not in dedicated repo)
- Rachel added 1 deleted label
added 1 deleted label
- Author Owner
As I got another similar issue with a one-to-one (with Rachel) this morning, I noticed some errors in the console. Current behaviour:
- Opened Firefox from fresh machine start
- Loaded https://community.startinblox.com
- Went to one-to-one channel with Rachel
- All but last message from Rachel disappeared from the history
- Got loads of errors in the console, see screen and copy:
XML Parsing Error: syntax error Location: https://community.startinblox.com/ Line Number 1, Column 1: community.startinblox.com:1:1 2020-04-24T07:50:48.072Z INFO: SASL authentication succeeded. <empty string> converse.min.js:1:513497 ERROR: Apparently we're no longer connected to MUC: f8im978oohvo@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="e7c28478-d85a-4af2-86ec-bb2cd63b182e:sendIQ" from="f8im978oohvo@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: lfm7bxksvvsu@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="5ad7b781-3762-4d32-96ca-f3baf916b30f:sendIQ" from="lfm7bxksvvsu@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: d9xmd0fmqxoa@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="dee8e2dd-74fb-4988-aa97-ac7a9deaf346:sendIQ" from="d9xmd0fmqxoa@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: fjivmrxotuqt@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="9bff8f6c-9b2c-473e-8105-bc9dd32a6fa1:sendIQ" from="fjivmrxotuqt@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: eqpajwqvkq4g@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="a1ce8569-a2d5-4d42-b23c-a3b733e5b56e:sendIQ" from="eqpajwqvkq4g@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: 5n2mo8yhlo1y@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="fa229ade-ced0-4e8b-8636-a32eb1c105d7:sendIQ" from="5n2mo8yhlo1y@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: d7rws9t9xfg2@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="2b90f654-059a-47e6-acfd-3802ab72a397:sendIQ" from="d7rws9t9xfg2@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Apparently we're no longer connected to MUC: s6hksacbwyns@conference.community.startinblox.com converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" xmlns="jabber:client" id="a3b0230c-74ff-47fc-92c8-0ee3c467f08b:sendIQ" from="s6hksacbwyns@conference.community.startinblox.com/balessan" type="error"><error type="cancel"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You are not currently connected to this chat</text></error></iq> converse.min.js:1:513203 ERROR: Error while fetching bookmarks converse.min.js:1:513203 ERROR: <iq to="balessan@community.startinblox.com/converse.js-36286347" id="0b0ab42d-7bf1-4318-8243-806d9ab8137b:sendIQ" xmlns="jabber:client" type="error"><error type="cancel"><item-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq> converse.min.js:1:513203 TypeError: e.querySelectorAll is not a function
@deleolajide don't forget to take a look at this one before starting something new :) Many thanks
- Rachel mentioned in issue #480 (closed)
mentioned in issue #480 (closed)
- Rachel mentioned in issue #494 (closed)
mentioned in issue #494 (closed)
- Guest
I have not been able to start on anything new due to the current issue with room activity indicators. I had a quick look at this and was unable to reproduce it. Maybe it is fixed with Firefox 76
- Rachel added 1 deleted label and removed 1 deleted label
added 1 deleted label and removed 1 deleted label
- Jean-Baptiste Pasquier unassigned @deleolajide
unassigned @deleolajide
- Jean-Baptiste Pasquier mentioned in issue components/solid-xmpp-chat#151
mentioned in issue components/solid-xmpp-chat#151
- Owner
Closing in favor of components/solid-xmpp-chat#151
- Jean-Baptiste Pasquier closed
closed