Hi Apple Devs,I recently finished a game for iOS, and I'm using TestFlight to have gamers test it before I release it to the public. I have a sign up sheet and I'm keeping records of testers' emails. When I'm ready to add testers in App Store Connect, I want to import a CSV to add them all instantly, as opposed to adding them one at a time. I can't find the formatting for CSV anywhere, not even in Apple's documentation. I know that they'll tell me what format it should be in when I have a build uploaded, but I don't want to have the wrong format and have to go back into my spreadsheet and modify all the cells. Does anyone know what the CSV formatting for importing testers should be? Something like email, first name, last name?ThanksJake

Hey Devs, I'm trying to sign up for the Small Business Program, and I had a question regarding the listing of Associated Developer Accounts. When they say "Do you have ultimate decision-making authority over another Apple Developer Program member account?", are they referring to any account including your own, or are they referring to other accounts that you have access to? Thanks!

Hi everyone. I recently submitted one of my Unity games for App Review today and it got rejected. The rejection was related to an In-App Purchase issue in iOS 15.3 (which, at the time of writing, is the latest version). Their response is below: We found that your in-app purchase products exhibited one or more bugs when reviewed on iPhone running iOS 15.3 on Wi-Fi. --Next Steps-- When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead. A couple things to note. I'm not even using server-side validation for my IAPs. For this particular game, I'm using local validation. My IAPs also worked in the sandbox environment. Both the test builds and production builds are running identical code. Any ideas on what could be causing this?