hello there sailors!
we have a number of pos extensions that are using the navigation API. we’re currently on v 2024.07.x for both packages:
"dependencies": {
"react": "^18.0.0",
"@shopify/ui-extensions": "2025.07.x",
"@shopify/ui-extensions-react": "2025.07.x"
},
And then in File A we use the api as:
const api = useApi<'pos.home.modal.render'>()
...
..
.
and then
<Screen
onReceiveParams={(params: { someParameter: boolean }) => params?.someParameter && setSomething(someParameter)}
>
Then File B, uses the same navitagion api to move back to File A screen:
const api = useApi<'pos.home.modal.render'>()
...
..
.
api.navigation.navigate('FileA', { someParameter: true })
BUT since the new ios shopify pos update with v10.19.x, this throw’s an error, saying that the
params are undefined.
Here’s the source code from the package itself:
export interface NavigationApiContent {
/** Navigate to a route in current navigation tree.
* Pushes the specified screen if it isn't present in the navigation tree, goes back to a created screen otherwise.
* @param screenName the name of the screen you want to navigate to.
* @param params the parameters you want to pass to that screen.
*/
navigate(screenName: string, params?: any): void;
/** Pops the currently shown screen */
pop(): void;
/** Dismisses the extension. */
dismiss(): void;
}
You can clearly see that there are params and I’m not crazy ![]()
Why break backwards compatibility? Or if you would have told us to migrate in a timely manner we would have (already planning to migrate to v2026.01), but as you can imagine every single piece of code needs to be touched.
react to preact and polaris components for everything instead of ui-extensions-react package.