Incorrect subscription pricing pulling from Apple

Also, I am testing on a real iOS iPhone 15 Pro Max device.  Also tested with the xcode sample app on my Mac.  Same deal.  My subscriptions are live, linked, the metadata lines up, I don’t understand where the hell it keeps pulling 9.99 and 79.99 from? 

I have not yet pushed the app into apple sandbox (test flight) yet.  I will be doing that as soon as I can get this figured out. 

Anyone go through this?  I see the documentation that states Testflight sandbox pricing could be off, but I’m still testing locally. Thank you!

https://www.revenuecat.com/docs/test-and-launch/sandbox/apple-app-store

Hi ​@mrb-consulting-services,

I’m sorry you are experiencing this issue! What’s the region of your sandbox account? Does that match the pricing in App Store Connect with the country storefront? Bear in mind that it’s expected that sometimes in sandbox currencies and prices are not correctly matching the ones in App Store Connect (see here). The reason is that while sandbox should behave identically to the App Store, it’s more flaky and inestable. 

Another thing to check, how are you reading and showing your prices in the paywall? If you are using RevenueCat paywall’s, which variables are you using?

Have you been able to try it in a completely different physical device? 

Best,

Hi, I was able to fix this.  Even though I set the product catalogs offerings identifier default to a new one I created, pointed to the app store data, it was trying to pull the data from the default one that is auto created when I first started the revenue cat account.  I simply removed that original product (which btw was still tied to my app store account, weird), and it started working.  

So I’m all good, I’m in test flight and every thing works beautifully!  I have my own native paywall page, native subscription page (after logging into the app to manage/view status).  It looks and works perfect.  About to go live this weekend with my app Chip In - Couples Financing. 

Hey ​@mrb-consulting-services,

Thank you for confirming that you were able to fix this issue. We are glad to know that everything is working as expected!
Best of luck with your release!