You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
There is a bug that causes unpinned objects to not beeing synced with new users.
To Reproduce
Steps to reproduce the behavior:
Log in with two browsers
Upload and pin a Media Object with BrowserA => BrowserA is owner and creator of persistent object
Reload the page with BrowserA => BrowserA gets a new userID (neither owner nor creator of object are connected)
Unpin the object with BrowserA => (this also takes ownership)
Refresh the page with BrowserA
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.
The text was updated successfully, but these errors were encountered:
Description
There is a bug that causes unpinned objects to not beeing synced with new users.
To Reproduce
Steps to reproduce the behavior:
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.
The text was updated successfully, but these errors were encountered: