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
When opening a scene with outdated dependencies, the "Loading failed" screen correctly shows the friendly "This scene's dependencies are out of date and don't support the Bevy renderer. Update them to continue." message with an "Update Dependencies" action button. However, the separate "New dependencies version detected β UPDATE" toast (bottom of screen) remains visible throughout the entire flow β during the Loading Failed state, during "Installing dependencies...", and even after the scene finishes loading successfully alongside a "Scene dependencies were updated" confirmation toast. The original toast is never dismissed, even though clicking its own "UPDATE" action (or the Loading Failed screen's "Update Dependencies" button) is what triggers the update that resolves it.
π£ STR:
Open a scene with outdated dependencies (predating Bevy renderer support)
Observe the "Loading failed" screen with "Update Dependencies" button, plus a "New dependencies version detected β UPDATE" toast at the bottom
Click "Update Dependencies"
Observe "Installing dependencies..." screen β the toast from step 2 is still present
Wait for the scene to finish loading
Observe the scene loads successfully with a "Scene dependencies were updated" confirmation toast β but the original "New dependencies version detected" toast is still showing alongside it
βοΈ Expected Result:
The "New dependencies version detected β UPDATE" toast should dismiss once the update is triggered (or once it completes), rather than persisting redundantly alongside the "Scene dependencies were updated" confirmation.
β Actual Result with evidence:
Toast persists across all three states β outdated-deps error screen, installing screen, and successful load β never dismissing on its own.
[Screenshots attached: Loading Failed screen, Installing dependencies screen, and loaded scene β all showing the persistent toast]
β Reproduction:
π Always
π₯οΈ Operative system and additional Notes:
Mac chip β M3.
Found while validating PR #1463, item "Outdated scene deps detection." Core fix (friendly message vs. raw CLI dump) works correctly β this is a follow-up polish issue on the notification lifecycle, not a regression of the fix itself.
π οΈ Build version:
Decentraland Creator Hub 0.45.0 (fix/bevy branch) β PR #1463
π Issue Description:
When opening a scene with outdated dependencies, the "Loading failed" screen correctly shows the friendly "This scene's dependencies are out of date and don't support the Bevy renderer. Update them to continue." message with an "Update Dependencies" action button. However, the separate "New dependencies version detected β UPDATE" toast (bottom of screen) remains visible throughout the entire flow β during the Loading Failed state, during "Installing dependencies...", and even after the scene finishes loading successfully alongside a "Scene dependencies were updated" confirmation toast. The original toast is never dismissed, even though clicking its own "UPDATE" action (or the Loading Failed screen's "Update Dependencies" button) is what triggers the update that resolves it.
π£ STR:
βοΈ Expected Result:
The "New dependencies version detected β UPDATE" toast should dismiss once the update is triggered (or once it completes), rather than persisting redundantly alongside the "Scene dependencies were updated" confirmation.
β Actual Result with evidence:
Toast persists across all three states β outdated-deps error screen, installing screen, and successful load β never dismissing on its own.
[Screenshots attached: Loading Failed screen, Installing dependencies screen, and loaded scene β all showing the persistent toast]
β Reproduction:
π Always
π₯οΈ Operative system and additional Notes:
Mac chip β M3.
Found while validating PR #1463, item "Outdated scene deps detection." Core fix (friendly message vs. raw CLI dump) works correctly β this is a follow-up polish issue on the notification lifecycle, not a regression of the fix itself.
07.08.2026_11.31.24_REC.1457.CH.ok.mp4
07.08.2026_11.33.59_REC.updte.dependencies.redundant.mp4