Cant use Admin::Product::Configuration::Render Extension Point

[marloeffler]

Hi, can somebody explain me, why we cant use

import {
  extend,
  render,
  Text,
  useExtensionApi,
} from '@shopify/admin-ui-extensions-react'
extend('Admin::Product::Configuration::Render', render(() => <App />));
function App() {
  const {extensionPoint} = useExtensionApi();
  return (
    <Text>
      `Welcome to the ${extensionPoint} extension`
    </Text>
  );
}

in our Developement Preview Store even if we have the option to create a Shopify private UI Extension? Everytime i want to follow this https://shopify.dev/docs/apps/selling-strategies/bundles/ui tutorial, it tells me

Admin::Product::Configuration::Render

isn’t supported, so do i miss something here?

[davidhollenbeck]

just want to bump this - getting same issue here using most recent CLI/shopify-app packages (3.46.5 as of now)

we also have already been approved for the bundle ui extensions but I submitted a second partner request.

[Luke-Clifton-HH]

Hi.

When i try and deploy a UI extension that is using the new Admin::Product::Configuration::Render extension point i get the following error:

Invalid extension point(s) configured: Admin::Product::Configuration::Render

I have already requested and been granted access to the Bundles UI extension CLI

I am also following this guide:
https://shopify.dev/docs/apps/selling-strategies/bundles/ui

Is there something else we need to configure or request access for?

[lizk]

Hi there

While the Bundles UI extension is in developer preview, you won’t be able to deploy the extension. Keep an eye on the documentation to know when deployment becomes available. I updated the documentation to make this more clear.

[shop_dev_35]

That makes sense to me, however when running locally, on my partner development store, (running npm run dev) I still get the following result:

Is there something I am missing? Why does the documentation say to deploy it first, and why wouldn’t this be allowed to be deployed if all the partner dev stores come with the Bundles UI extension developer preview enabled? Just curious if any documentation can be updated to match the output shown in some of the examples? It is hard to truly begin building in this extension if I can’t properly test the initial setup. Any help would be appreciated, thank you!

[marloeffler]

This whole thing is just a joke. Announced on Jan this year, cant be used in July.. even our partner manager has no clue. I am just frustrated.

i hope this will be sorted out, otherwise i just give up on bundles.

[davidhollenbeck]

I’m sure it will be addressed

This is such a massive change to how product data is going to be handled across the platform, I honestly wouldn’t be surprised if it gets pushed back a quarter. Remember when online store 2.0 got delayed a whole year…but they rolled it out with 0 breaking changes. Worth the wait for sure

[marloeffler]

yeah, i know. But the communication on this is just really bad.

[lizk]

Thanks for flagging Shop_dev_35!

The team is aware and working on a fix for this!

[shop_dev_35]

Just wanted to ask if this is considered a bug or is this expected? If it was expected, then why have the docs have the tutorial? Is there currently the UI portion of this tutorial available to view in Github or something like that?

[davidhollenbeck]

The documentation was recently updated to add some missing config variables and clarify that this is still in preview mode

[shop_dev_35]

I saw that already, and even before they updated the docs I already had the .toml file updated with the config needed for this. However no matter what I change, on any file, when I run dev locally, the extension point never renders, and always gives me the “unsupported extension point” error. With no further logging to reference.

Either I am not running my app / extension correctly in dev, or I have some piece of the extension incorrectly configured, or this is just a flat out bug. If it is just a bug, then, in all honesty, the tutorial needs to be removed or modified more to explain what is happening. What is the point of a dev preview if the preview doesn’t actually work due to a bug? That is why I was asking if this is a bug or not, so I can investigate further and continue debugging/dev. I Would like a resolution (or at least more detailed information) sooner than later so dev work can be finished around the time of the full release.

[davidhollenbeck]

We are in the same boat - tbh I haven’t had a chance to try with the updated docs. Support told me they also updated the codegen so was going to look into that

Tbh, if you look at the extension point used in the default bundles app, it just opens up a modal in App Bridge. My team decided to just ignore the UI extension requirement and build an interface in the traditional embedded UI w/Polaris - we will adapt our logic whenever this is ready for production

[shop_dev_35]

With the 23 summer edition announcement we see that the admin.product-details.configuration.render extension point is available, however I still don’t see what this extension point renders within the admin product details page? Is this supposed to be used within the app page to create a product configurator? If so, why does the extension link, link to the products page within the admin, and why does it not render anything? Isn’t this supposed to render something on the admin product details page? If so what is it supposed to render? I don’t see any of my tests rendering anything on the admin product details page unless I change it to use the admin.product-details.block.render extension point. I guess I am a bit confused on what the admin.product-details.configuration.render actually is targeting.

Im excited for the new things being released and excited to work with these extension points for the shopify admin, but just failing to understand if some of these things are bugs, or if I am misusing these extension points. The docs don’t specify much for the admin product extension points outside of the subscription app examples. Any insights would be greatly appreciated.

[marloeffler]

You can see the ‘admin.product-details.block.render’ thats alot more then we can see. Have the same problem with the ‘admin.product-details.configuration.render’ it just wont display.

[shop_dev_35]

@lizk Honestly is there any update on this? Or at least going to be? I see the docs updated, and saw the PR’s in the Shopify extension-templates github last month. However the admin.product-details.configuration.render still does absolutely nothing. So im trying to do a work around, and that is fine, but I don’t want updates to this extension point or the admin.product-details.block.render extension point to break my workaround. Are you guys favoring your fixed bundle app over letting us build a customized bundle configurator UI? Is there just no demand for this extension point?

Im just so confused at this point. We have the promise of customized bundles, somewhat, and the cart transform function works fine, but the customized bundle concept isn’t THAT different from just creating a fixed bundle. But that is irrelevant to this issue I suppse. As a dev, I am feeling held back a bit, if these extension points are not ready, then why even release the dev docs? I am now creating solutions with one arm behind my back when trying to build a UI for my clients to ensure they can configure customized bundles more effectively. Im not trying to pressure any devs or trying to claim you guys at Shopify are doing a poor job or to sound ungrateful for all of these latest updates, I am just trying to better understand so I have a clear concise explanation to my team, and can know if my work arounds / alternative options for these extension points will last as I continue to build on them. Any info would be helpful. I appreciate it.

[lizk]

Hi @shop_dev_35

Thanks for the ping. You should be able to use the admin.product-details.configuration.render extension point. I just tested it myself, and was able to get the extension point to render in the Shopify Admin.

Something that is different about this extension point it that the extension will only render if the app that is associated with the extension, is also the “owner” of the product. In this case that means has also created the associated bundle. I know this is not clear in the documentation so I will look into getting this updated ASAP.

Let me know if that doesn’t resolve the issue.