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

Object inconcistency between users. #5586

Open
CodingBitsDev opened this issue Jul 14, 2022 · 2 comments
Open

Object inconcistency between users. #5586

CodingBitsDev opened this issue Jul 14, 2022 · 2 comments
Labels
bug P1 Address as quickly as possible

Comments

@CodingBitsDev
Copy link

Description
There is a bug that causes unpinned objects to not beeing synced with new users.

To Reproduce
Steps to reproduce the behavior:

  1. Log in with two browsers
  2. Upload and pin a Media Object with BrowserA => BrowserA is owner and creator of persistent object
  3. Reload the page with BrowserA => BrowserA gets a new userID (neither owner nor creator of object are connected)
  4. Unpin the object with BrowserA => (this also takes ownership)
  5. Refresh the page with BrowserA
  6. The Media is still visible for BrowserB but BrowserA doesn't nor any updates of it.

Expected behavior
The object should either be deleted for both browsers, or better be synced with both browsers.

Hardware
Testet with chrome and Oculus Browser. It should however exist in every browser since it is caused by code in Networked aframe.

Additional context
This is caused by networked-aframe. Users are only allowed to sync networked objects if they are either the owner, or the creator of an object. Neither of those users are online after following the steps above.

I will in soon make a pull request to solve this issue.

@CodingBitsDev CodingBitsDev added bug needs triage For bugs that have not yet been assigned a fix priority labels Jul 14, 2022
CodingBitsDev pushed a commit to CodingBitsDev/hubs that referenced this issue Jul 14, 2022
@CodingBitsDev
Copy link
Author

Merge requst can be found above
#5587

@emclaren
Copy link
Contributor

thanks for looking into this. Our team ran into this issue the other day as well

@emclaren emclaren added P1 Address as quickly as possible and removed needs triage For bugs that have not yet been assigned a fix priority labels Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug P1 Address as quickly as possible
Projects
None yet
Development

No branches or pull requests

2 participants