What changed
The POS Navigation API adds the navigatesuccess event. It fires after the destination screen finishes its native transition, and its callback receives a standard Event.
currententrychange can fire before the screen finishes appearing, and the navigate() promise doesn’t wait for the transition. When navigating back, register the listener on the screen that will reappear; the screen being left is removed.
Who’s affected
The event is available to POS UI extensions that target API version 2026-10 and run on POS builds that support it. Older POS builds won’t emit navigatesuccess.
What to do
No migration is required. To act after a screen finishes appearing, listen for navigatesuccess. Don’t use the navigate() promise as a signal that the native transition has finished.
Was this page helpful?