Bug in POS ext: relative URL fetch resolves incorrectly

Hi folks,

in 2025-07 API release, POS extensions added support for fetch requests using relative URLs, which should resolve to the app URL. However, it looks like they’re incorrectly resolving to the store’s myshopify.com domain instead. Could you please fix this issue? Thanks!

Hey again @Patrick_Jakubik, thanks for flagging this. This definitely sounds off and could potentially be an issue on our end here.

Would you be able to share a quick code snippet of the fetch call (like a minimal repro), any console or response errors you’re seeing. If possible, a short screen recording of it happening would be super helpful if you can reproduce it locally. Once we have that, I’ll dig in right away and keep you posted - hope to hear from you soon.

Hi @Alan_G

Here you go:

fetch("/api/testing")

Hi @Patrick_Jakubik, thanks for your report! The fix for development mode extensions resolving the appURL incorrectly will be in POS version 10.8, which is currently scheduled for rollout to be complete on August 13. This issue only affected extensions in development mode, so any deployed extensions should work as expected. As a temporary workaround, you might try deploying your app as a staging app, install and activate it, and test using that before deploying your app as a production app.

2 Likes