Currently, I'm mixing the Swift and C sources to assemble a single framework. To do so, I already made a modulemap for each of a module, and build & import to an app bundle is fine. WORKSPACE structure: Tester App (Framework-importing-app) Framework But the problem here is, when I try to import it into OTHER app, it cannot find ANY of C-generated module (All swift module are fine). What's happening here? do I miss anything?

Hello, all developers. I have some questions about code signing strategy, according to the sequence of signing (which I couldn't reached the answer by searching). That is, What happens when we DON'T provide any code signing identity and profile on ARCHIVE, and then we DO provide them on EXPORTING step? for example, xcodebuild archive \ -project <ProjectName>.xcodeproj \ -sdk iphoneos \ -scheme <SchemeName> -configuration Release \ CODE_SIGN_IDENTITY="" \#disable code sign CODE_SIGNING_REQUIRED=NO \#disable code sign CODE_SIGNING_ALLOWED=NO \#disable code sign Above is the code for archive without code sign. And below, for exporting, I provide profile using exportOptions.plist. xcodebuild -exportArchive -archivePath <ProjectName>.xcarchive -exportOptionsPlist <ProjectName>/exportOptions.plist -exportPath <ProjectName>.ipa Is this available for app-store distribution, if I used profile with distribution option? Are these right option to provide details of provisioning profile, when archiving the project? I've search lots of examples but the answers are slightly different. xcodebuild archive \ -project <ProjectName>.xcodeproj \ -sdk iphoneos \ -scheme <SchemeName> \ -configuration Release \ CODE_SIGN_IDENTITY="****D21C78" \ PROVISIONING_PROFILE="********-****-..." the code above keeps making the error : <ProjectName> requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor, even though I'm working on CLI. If there's any solution for questions, please guide me. Any document / paper or other materials are fine too.