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

Testing site broken (private chatroom not syncing across devices) #2066

Closed
taoeffect opened this issue Jun 14, 2024 · 2 comments
Closed

Testing site broken (private chatroom not syncing across devices) #2066

taoeffect opened this issue Jun 14, 2024 · 2 comments

Comments

@taoeffect
Copy link
Member

Problem

  1. While desktop computer was asleep, I created a private chatroom on my phone via the PWA
  2. Posted a few messages to it
  3. Woke up computer and did not see the chatroom listed. No errors in console. Refreshing page doesn't fix it! However, opening a private window and re-logging in there does show the private chatroom.

Phone PWA:

tmp-1718337318871

Desktop:

Screenshot 2024-06-13 at 8 54 54 PM

Solution

Find and fix the problem.

@corrideat
Copy link
Member

Are you able to reproduce this, or do you have a copy of the state or logs?

corrideat added a commit that referenced this issue Jun 17, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
corrideat added a commit that referenced this issue Jun 17, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
corrideat added a commit that referenced this issue Jun 17, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
corrideat added a commit that referenced this issue Jun 18, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
* Increase shelter header validity window
corrideat added a commit that referenced this issue Jun 18, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
* Increase shelter header validity window
taoeffect pushed a commit that referenced this issue Jun 18, 2024
* eventsAfter: Reject early if the contractID is not set
* Fix instances causing such unset contractIDs
* Fix group members list to include members with only a contractID
* Don't set an empty contract state when receiving OP_KEY_SHARE
* Files: laxer validation when removing to process individual files separately
* Increase shelter header validity window
@taoeffect
Copy link
Member Author

Re-opening this as I'm not convinced it's fixed and making it depend on #2110 being closed.

@taoeffect taoeffect reopened this Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants