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
I think we briefly discussed this before. To me it doesn't look like a race condition but it's a persistent issue, that causes quite some confusion in demos (and presumably also for actual users).
The text was updated successfully, but these errors were encountered:
## **Description:**
Closes#1348
This PR addresses a persistent UX issue described in #1348, where the
extension would not switch to the newly created account after the user
completed the creation flow.
### Context
The problem was caused by missing handling in `useLaunchRoute` for the
case where a new route is created (i.e. the `routeId` differs from the
current `activeRouteId`). While the `onLaunch` callback was invoked, no
navigation was triggered, leaving the extension and UI in an
inconsistent state.
### Changes
- Updated `useLaunchRoute` to differentiate between updating an existing
account vs. creating a new one.
- When a new route is detected, we now:
- Invoke the `onLaunch` callback (as before),
- Immediately navigate to the corresponding route.
- For existing routes with pending transactions, we preserve the
existing behavior and prompt for user confirmation.
---------
Co-authored-by: Philipp Giese <[email protected]>
I think we briefly discussed this before. To me it doesn't look like a race condition but it's a persistent issue, that causes quite some confusion in demos (and presumably also for actual users).
The text was updated successfully, but these errors were encountered: