Unified polaris admin extension no longer working

Extensions
1

Hey folks!

We’ve been building off of the UNIFIED/web components api_version 2025-10 for a post purchase option admin ui extension. It was working fine about 3-4 weeks back and we had finished most of the implementation.

Starting around 1-1.5 weeks ago, the api_version 2025-10 disappeared, and we got an error on the latest Shopify CLI that it should be either “latest” or “unstable”. Around the same time, an error now appears when trying to access our custom UI on the edit product page. When we try to open a previously created purchase option (which would load our custom UI) it now throws an error in the browser console:

Uncaught (in promise) Error: [TARGET MISMATCH] The target in shopify.extension.toml ‘admin.product-purchase-option.action.render’ does not match any targets specified in the extension module: []

We’ve tried switching to unstable, and combed through as much of the GH changelogs, issues, PR’s, updating the CLI and everything else we can think of - but the UI we had developed and had working with the new unified components no longer loads all of a sudden.

Does anyone know if there has been any changes to allowing development using the UNIFIED lib/preact - and if there’s a way to continue to do so at the moment?

Cheers,

2

@Simon_Porter - did you ever find a resolution to this? i’m having the same exact issue

3

@Matthew_Tucker did not I’m afraid! As it was working before when we did the initial implementation (for quite some weeks) I was hoping this would eventually resolve itself over time. Still no luck yet though. I also tried in partners Slack but that didn’t get any bites either.

4

@Simon_Porter gotcha - thanks for the update. Hopefully it will be resolved in future releases. I will let you know if I figure anything out!

5

Hi Simon, Thank you for reporting the bug. We’re working on a fix - I’ll keep you posted.

6

Thanks Trish! Great to hear. If you need me to test anything or more info. I’m also on the partners Slack for more realtime testing, but happy to watch for updates here too.

Looking forward to what you find.

Cheers,

7

@Simon_Porter can you try again now? The issue should have been resolved now

8

Hey @Trish_Ta , thanks very much. I can confirm that “2025-10” is now available again as an api_version, and that has allowed the extension to start working again.

Cheers!