Hi Albert I went through Ed's post; basically, he is talking about how to embed the frameworks. In our case, this isn't about embedding the frameworks we have developed or even third party frameworks. It's likely about the Swift system libraries provided by Xcode, probably to support older iOS versions. As pointed out in Ed's post - iOS, watchOS, and tvOS support third-party frameworks but don’t support third-party standalone dynamic libraries—those outside a framework bundle, typically with the .dylib filename extension. The only exception to this rule is the Swift system libraries provided by Xcode. Our application deployment target is set to 13.0. We have started using Declared AgeRange Framework (Swift ONLY API) to comply with the upcoming state law. Declared AgeRange is an asynchronous API and our application uses await/Async. Initially we encountered a TestFlight error regarding the missing SwiftSupport folder. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing We resolved this error by generating an Archive using Development environment and then extract an IPA using Distribution method. The resulting IPA contained the SwiftSupport folder that App Store Connect expected. method app-store-connect FYI, this occurs when we generate an Archive using the Development environment and then extract an IPA using the development method. The resulting IPA did not have the SwiftSupport folder. method development The new observation is that uploading the application to TestFlight was successful. But the minute we add testers and submit for review, the application binary state shows "invalid binary" as seen in the attached screenshot. What causes the application binary state to become "invalid binary"? Could you please help here on this. Regards, Chethan