This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 70%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
I have an app that has been published (privately) to the Windows Store. The app has a store-managed consumable add-on that has also been published.
The add-on does not show up in the store on the app page. The app shows up.
Both have the same audience groups.
When I click on the store link for the add-on that is given by partner center, it says "We are sorry, the page you requested cannot be found."
I tried resubmitting an "update" to the add-on. It was approved and published. Still doesn't work
What would cause this?
How can I fix it?
How do I get real support for this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 92%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Could you please take a look at the add-on status in the Application overview Page in the Partner Center? What's the status of that add-on? Another thing is that there might be a time delay about 24-48h after your add-on is successfully published and before you could see it in the store. If your add-on is successfully published, please try to wait for 24h and check the status again.
Hi, Thank you for your response.
The status shows "In the Microsoft Store" This was published on 10/27/2021. The link still does not work - I made sure to paste it into a browser where I was already logged into the Microsoft Store with an approved e-mail address...
Do you have other ideas why it might not show up?
Thank you!
Is it possible for me to DM you a link to investigate?
one other point -- when I use the StoreContext.RequestPurchaseAsync with the same store product Id, it (correctly) pops up the store interface for the user to make the purchase.
Could you please tell me what is the link that you mentioned? Is that the link in the Application overview Page in Partner Center Dashboard? So the add-on could be purchased in your app successfully, right?
The link is under Submissions, Pricing and Availability, for the add-on in partner center. It looks like this:
https://www.microsoft.com/store/r/<Add-On Product ID>
@Jeff C Do you have any other add-ons? Do other add-ons have the same behavior? Or does it just happen to that add-on only? I want to confirm if this is a single issue or it affects all of your add-ons,
I have one other add-on, though I do not use it in my application. It is a developer-managed consumable, and it has the same behavior -- the link does not work.
I'm also having another HUGE problem! Many of my users are sometimes unable to purchase the add-on through the in-app purchase. I will post a separate thread about that.
"PUR-EntitlementsError"
It happens repeatedly and for different users.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 78%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Hi, I also have this problem. I want to allow my add-on to be purchased directly through the store. But the add-on does not appear in the store. I have followed all the proper steps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 9%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
I have the same problem. First add-on is available only through in-app purchase, and works well with the API. Second add-on is only available to a private group on the Store, with me included in the group. It does not show up in the Store on the application page. Did anyone find a solution to this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 14.000000000000002%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi I was just wondering if you guys ever came to a conclusion on this topic. I'm having the exact same issue. My add-on was published to a private audience with a handful of email accounts in the group, and the link provided on the "Pricing and availability" page does not work for any of them, instead leading to a "We are sorry, the page you requested cannot be found". Its status has been "In the Microsoft Store" for ~4 days now.
Similarly I have selected for the add-on to display on the parent application product page, and it is no where to be seen there either. In my application I was hoping to link to the Microsoft Store purchase page directly, rather than using StoreContext.RequestPurchaseAsync as my application is a stand alone widget.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 39%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
does any one arrived to solve this issue? my newly created add-on have the same behavior...