Sidekick URL fails to navigate SPA when query parameters are included

Extensions
1

For some reason, when using Sidekick tools and having it render a link to my app (NextJS 16.3 using pages router), it will update the top url correctly when clicked, but the app doesn’t actually route anywhere. When there’s no query parameters in the URL it works fine.

2

It seems to work the first time, but if you navigate in the app and try to click the link again it doesn’t work.

3

What good are these tools anyway? Apparently I’m not allowed to have a tool that just opens a page in my app? I can’t have a tool that helps the user construct a task? Read-only is such a lame thing. I will probably just make my own AI assistant in the app.

5

Hey @DavidT, thanks for flagging. I took a look here, and something does seem odd if the Admin URL updates but the embedded app stays on the previous route.

Could you share:

  • The sanitized result object/URL and extension target you’re using.
  • window.location.href and Next’s router.asPath after the failed click.
  • Your App Bridge version.

That should confirm whether the navigation isn’t reaching the iframe or Next is receiving it without updating. I’ll dig further on our end once we have that. Hope to hear from you soon!