My pos.post.purchase extension targets are not rendering after completing a transaction on the live store.
This does not occur with the development store, which works as intended. Both releases use identical code (outbound URLs determined via session IDs).
I was just wondering if anyone has encountered this before and if there were any known causes or fixes.
Just to reiterate, my development store and the live store use identical builds, so I’m scratching my head at what the issue could be. TOML malformation would be an issue on dev store too, but that’s not the case.
I’m sure it’s something that will feel incredibly obvious afterwards, but I have never experienced an issue with extension targeting between dev and live version.
I am afk at the moment, but I will happily share anything that can help diagnose the issue when back at my desk.
I feel like a fool lol. Thank you so much, Nathan. I had forgotten that the development preview delivers all extension targets upon scanning the qr code.
Enabling these targets through the merchant’s admin worked like a charm.
I’m sorry, but this default configuration doesn’t make sense to me. If a user has decided to install the application, why should they have to enable the available areas manually afterward? If the app has configured those additional areas and the user has installed it, they should be enabled by default.
When migrating old POS Links to new POS UI Extensions, if my app is deployed to 20 shops, I need to provide additional details to merchants so they can continue using my application in the same way. This is far from ideal.
