Post

Replies

Boosts

Views

Activity

For a Non-Renewing Subscription the price appearing different from what we set on App Store Connect and the TestFlight (iPhone and iPad)
Hi Team, Issue general Description: For a Non-Renewing Subscription (1 year regular subscription) we have chosen the price tyre 8 which is £ 6.99, but the price displayed on the device/simulator during TestFlight testing is £ 7.99 which is incorrect and not expected as well. Steps to reproduce the issue: For an existing Non-Renewing Subscription set price tyre 8 which is £ 6.99. Download the app through TestFlight which has the current configuration to get the above subscription. While moving into the subscription page it should display the price as £ 6.99, but it shows £ 7.99 What we expect to happen! If we set the price tyre on App Store Connect to tyre 8 which is £ 6.99 we expect to see the same price (£ 6.99) for UK store on the device which download the app from TestFlight. What actually happened! If we set the price tyre on App Store Connect to tyre 8 which is £ 6.99 we expect to see the same price (£ 6.99) on the device which download the app from TestFlight. But it shows £ 7.99, which is potentially incorrect. Quick turnaround would be really appreciated. Best regards. Achuthan
2
0
648
Aug ’22
No warning email received from Apple even though we upload an app version WITHOUT Privacy manifest
Being a software company we create and distribute an iOS SDK with our customers world wide. The distribution of the software is in the form of a static library / XCFramework to our customers. They will integrate the SDK and use it to collect data from their hosting as first party. As Apple enforced through this article “Describing use of required reason API” - “starting from Fall 2023 you’ll receive an email from Apple if you upload an app to App Store Connect that uses required reason API without describing the reason in its privacy manifest file”. We are using "NSUserDefaults” in our SDK which is one among the required API listed, and as of now we didn’t create a Privacy manifest file and declared this on the SDK. We tried uploading our app to the Appstore connect portal, as we are not complying with the requirement from Apple we expect to see the warning message. Currently we are unknown about the impact of not having the Privacy manifest, and we would like to test the scenarios and make sure we are declaring the correct information on our SDK. Please could you review this and let us know why we are not receiving the emails. Or is that Apple didn’t harden the uploads yet and something planned for future date?
2
1
1.9k
Nov ’23