I am having the same experience. I created a sticker pack one week and then I was not able to after. Between these two periods I installed an updated version of XCODE and upgraded the OS. I'm on: XCode 13.1 (13A1030d) Monterrey 12.0.1 What is your systems configuration? 2021-11-03 18:09:23.132166-0500 StickerPackExtension[5754:2679938] [PPT] Error creating the CFMessagePort needed to communicate with PPT. Interestingly, when trying to run the sticker package project created prior to the updates, that works just fine. I'm thinking something was messed up with the last Xcode update.

I'm having the same issue. My application should have a price of 5.49, but it is appearing as 0.49 in the sandbox and my application is not being approved because of this.

Does anyone know what team can help? Who we need to raise a support ticket too? This is keeping my application from being approved. The AppConnect Review group are stating I'm violating the policy. The policy they referenced is: Guideline 3.1.2 - Business - Payments - Subscriptions The billed amount of your auto-renewable subscription does not match the amount displayed on the Subscriptions page. Has anyone else experienced this?

@Franky11 - Thanks for providing some additional context on your experience. On my end, I've not changed any prices. The issue presented itself after my last release and its review. Approximately Nov 15. Maybe we can start to collect some notes from each of our experience to see when this started happening? Maybe we can take it to support then? I have a feeling that the AppleConnect review team and the other support teams are not talking to each other. If the bug was communicated to the review team, maybe they would allow our apps to move forward in the review process? I do understand though that they want to ensure everything is correctly implemented before releasing a new product version.

I have not had any update to the FB ticket I raised. Has anyone else here? I may need to raise a TSI.

I solved the issue. There was a bug where in some cases the app group was not populated correctly and this caused the widget to appear as a placeholder. Very funny bug and the logs and error logs showed no indication on what the issue was. I hope this helps someone.