Open CH with User A and Open Explorer with User B

Oct 13, 2025 by recoveryshake.com 25 views

Introduction

In the Creator-Hub, a collaborative platform for creators to share and showcase their work, a critical issue has been reported. When two users, User A and User B, are present in the same environment, User B is unable to see the deploy changes made by User A. This issue affects the core functionality of the platform, hindering collaboration and communication among users. In this article, we will delve into the details of this issue, explore the steps to reproduce it, and discuss the expected and actual results.

Issue Description

When two users, User A and User B, are present in the same environment, User B is unable to see the deploy changes made by User A. This issue is critical, as it affects the core functionality of the platform, hindering collaboration and communication among users.

Steps to Reproduce (STR)

To reproduce this issue, follow these steps:

Open CH with User A and Open Explorer with User B: Open the Creator-Hub with User A and open the explorer with User B.
Deploy a Scene with User A: Deploy a scene with User A.
Go to the Land with User A: Go to the land with User A.
Open Another Tab/Explorer with Player B: Open another tab/explorer with Player B.
Go to Player's A Location: Go to Player A's location.
Check that the Updates are Not Registered by User B: Check that the updates are not registered by User B.
Close and Re-Open the App with Player B: Close and re-open the app with Player B.
Once You Open Go to the Deployment's Location: Once you open, go to the deployment's location.
Check the Changes: Check the changes.

Expected Result

The expected result is that User B should not see the deploy changes made by User A.

Actual Result with Evidence

The actual result is that both users should be able to see the deploys.

Evidence:

Player A

Player B

Repro Index

The repro index is 10/10, indicating that this issue can be consistently reproduced.

Operative System and Additional Notes

This issue occurs on both platforms.

Analysis and Discussion

The issue of User B not seeing the deploy changes made by User A is a critical one, affecting the core functionality of the platform. The steps to reproduce this issue are straightforward, and the expected and actual results are clear. The evidence provided in the form of images from Player A and Player B's perspectives highlights the issue.

Possible Causes

There are several possible causes for this issue, including:

Inconsistent Data: Inconsistent data between User A and User B's environments may be causing the issue.
Network Issues: Network issues may be preventing User B from seeing the deploy changes made by User A.
Platform Bugs: Platform bugs may be causing the issue.

Recommendations

To resolve this issue, the following recommendations are made:

Investigate Inconsistent Data: Investigate inconsistent data between User A and User B's environments to determine if this is the cause of the issue.
Check Network Issues: Check for network issues that may be preventing User B from seeing the deploy changes made by User A.
Fix Platform Bugs: Fix any platform bugs that may be causing the issue.

Conclusion

In conclusion, the issue of User B not seeing the deploy changes made by User A is a critical one, affecting the core functionality of the platform. The steps to reproduce this issue are straightforward, and the expected and actual results are clear. The evidence provided in the form of images from Player A and Player B's perspectives highlights the issue. To resolve this issue, it is recommended to investigate inconsistent data, check network issues, and fix platform bugs.

Future Work

Future work on this issue should include:

Investigating Inconsistent Data: Investigate inconsistent data between User A and User B's environments to determine if this is the cause of the issue.
Checking Network Issues: Check for network issues that may be preventing User B from seeing the deploy changes made by User A.
Fixing Platform Bugs: Fix any platform bugs that may be causing the issue.

Q&A

Q: What is the issue with the Creator-Hub platform? A: The issue is that when two users, User A and User B, are present in the same environment, User B is unable to see the deploy changes made by User A.

Q: What are the steps to reproduce this issue? A: To reproduce this issue, follow these steps:

Open CH with User A and Open Explorer with User B.
Deploy a scene with User A.
Go to the land with User A.
Open another tab/explorer with Player B.
Go to Player's A location.
Check that the updates are not registered by User B.
Close and re-open the app with Player B.
Once you open, go to the deployment's location.
Check the changes.

Q: What is the expected result of this issue? A: The expected result is that User B should not see the deploy changes made by User A.

Q: What is the actual result of this issue? A: The actual result is that both users should be able to see the deploys.

Q: What evidence is provided to support this issue? A: Evidence is provided in the form of images from Player A and Player B's perspectives, showing that User B is unable to see the deploy changes made by User A.

Q: What is the repro index of this issue? A: The repro index is 10/10, indicating that this issue can be consistently reproduced.

Q: What are the possible causes of this issue? A: Possible causes include:

Inconsistent data between User A and User B's environments.
Network issues preventing User B from seeing the deploy changes made by User A.
Platform bugs causing the issue.

Q: What recommendations are made to resolve this issue? A: Recommendations include:

Investigating inconsistent data between User A and User B's environments.
Checking for network issues that may be preventing User B from seeing the deploy changes made by User A.
Fixing platform bugs that may be causing the issue.

Q: What is the conclusion of this issue? A: The issue of User B not seeing the deploy changes made by User A is a critical one, affecting the core functionality of the platform. The steps to reproduce this issue are straightforward, and the expected and actual results are clear. The evidence provided in the form of images from Player A and Player B's perspectives highlights the issue.

Q: What is the future work on this issue? A: Future work on this issue should include:

Investigating inconsistent data between User A and User B's environments.
Checking for network issues that may be preventing User B from seeing the deploy changes made by User A.
Fixing platform bugs that may be causing the issue.

Q: How can this issue be resolved? A: This issue can be resolved by following the recommendations made to investigate inconsistent data, check network issues, and fix platform bugs.

Q: What is the impact of this issue on the Creator-Hub platform? A: This issue affects the core functionality of the platform, hindering collaboration and communication among users.

Q: How can users report this issue? A: Users can report this issue by following the standard reporting procedures for the Creator-Hub platform.

Q: What is the estimated time to resolve this issue? A: The estimated time to resolve this issue is dependent on the complexity of the issue and the resources available to resolve it.

Q: Who is responsible for resolving this issue? A: The development team is responsible for resolving this issue.

Q: What is the next step in resolving this issue? A: The next step in resolving this issue is to investigate inconsistent data between User A and User B's environments.