app-store-connect | A SDK based on Vapor for App Store Connect API | REST library

I have followed the codelabs to integrate in app purchases in flutter here https://codelabs.developers.google.com/codelabs/flutter-in-app-purchases#0

Also read the official documentation https://pub.dev/packages/in_app_purchase.

I have the app working fine in development. The products are properly fetched from both stores (app store and google play) and test payments are being done in both platforms:

• In google play, with the test card
• In app store by using the tester account (https://help.apple.com/app-store-connect/#/dev8b997bee1)

Yet I don't not what else I need to do before rolling the apps into production. I am afraid somehow the test configuration will prevail and actual users will purchase for free on production. I cannot see anywhere a configuration where I could easily turn a switch from test/sandbox to production.

What am I missing?

I'm trying to sign the iOS build on Codemagic using YAML workflow. Following this document I encrypted and added the following environment variables:

1. APP_STORE_CONNECT_KEY_IDENTIFIER
2. APP_STORE_CONNECT_ISSUER_ID
3. APP_STORE_CONNECT_PRIVATE_KEY
4. CERTIFICATE_PRIVATE_KEY

On running the workflow I'm getting error Provided value "VALUE of APP_STORE_CONNECT_PRIVATE_KEY" is not valid. What to make this env variable value valid? I also tried adding base64 encoding for this value, but it still shows the same error.

Here's my codemagic.yaml file:

I'm having trouble uploading App Previews in App Store Connect. Despite following all of Apple's specifications, App Store Connect rejects the file with messages like:

• "Your app preview is too large" (despite it being way below the max size of 500MB)
• "The dimensions of one or more previews are wrong" (despite them being correct)

This happens either as soon as I start uploading the file or after it has finished processing.

It also happens for both supported formats: H.264 and ProRes 422 (HQ). I have tried using about 10 different export presets for the file, and even tried re-converting my (already compliant) video editor output with ffmpeg, but no luck.

I'm about to publish my ios app to the App Store, but I don't know how I should fill out the Apple App Privacy in App Store Connect. I use admob, firebase analytics, firebase crashlytics and firebase authentication in my app. I've found this website that shows how to fill out the app privacy for admob, but I couldn't find one for firebase analytics or firebase crashlytics.

Do you know any website or tutorial that shows how to do fill out the app privacy for firebase analytics and firebase crashlytics? or if you've published an app to the App Store, can you tell me how you do it for your app?

How the phased rollout of App Store Connect works in detail? The official Apple documentation is very poor and doesn't mention a lot of things that matter. Let me formulate some questions.

The situation

1. The current version of my app is 1.0 and is released to everyone in the App Store. The version I want to release is 2.0 (Build number: 100) and is a major update with breaking changes
2. I start a phased release for version 2.0
3. After 2 days the update has reached 2% of my users (randomly selected) with automatic updates turned on. I decide to pause the release because I found a critical bug
4. I create a version 2.0.1 (Build number: 101) with the bugfix to 2.0
5. I create a version 1.0.1 (Build number: 102) with intent to rollback to 1.0 in case the major update it's not going well

Questions

1. How does the release of an update work during a phased release? Will version 2.0.1 be released only to the same 2% of the users that already received version 2.0? Or it will be delivered to a completely new 2% of my users?

2. In case it's a new 2% of users:

   2.1 what happens to the 2% of users that are on 2.0 and to the remaining 98% that is still on 1.0?

   2.2. is it true that is completely new 2%? Because if they are randomly selected, potentially there could be an intersection between the old 2% and the new 2%.

3. In case I don't want to proceed with the release of the bugfix 2.0.1 (e.g. I realize that the major update 2.x is not behaving well), what is the strategy to rollback to version 1.x? How can I push 1.0.1 to everyone? Should I cancel the phased released of 2.0 and just submit 1.0.1?

Thanks in advance for the help! I have read tons of Stackoverflow posts and I have tried to look everywhere on the web, but I didn't find any clear answer about the topic above.

I am trying to upload my build to iTunes connect, but from this morning I see this error:

ERROR ITMS-90744: "Unsupported Xcode or SDK Version. Your app was built with a version of Xcode or SDK that is not yet supported for upload to App Store Connect. For more information about supported versions of Xcode and SDK for Testflight or App Store submissions, view the App Store Connect What's New page (https://developer.apple.com/app-store-connect/whats-new/)."

I have the latest beta MacOS 11 (Big Sur), and latest Xcode Version 12.0 beta 3 (12A8169g)

Screenshot

I am trying to test in-app purchases on an iOS device. At Create a sandbox tester account it says:

To connect to your development servers and the test environment for the App Store, run a development-signed version of your app and sign in using a sandbox tester account.

The problem is, I don't know what a "devepment-signed version" is, or how to run one.

In Xcode I have one app target, and under "Signing & Capabilities", "All", "Debug" and "Release" have "Automatically manage signing" checked. I cannot find a way to run a "development-signed" version and am not having luck figuring this out by Googling. Does this have to be a physical device, or can it be a simulator?

I am trying to add individual testers to my app in Testflight, but I am not seeing an "Invite" button described in the documentation. Any ideas?

Docu: https://help.apple.com/app-store-connect/#devf096f25de