XCFramework archive - No such module on import AppAuth / AppAuthCore
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
We are building our SDK via xcodebuild archive and we have a dependency on AppAuthCore (but have the same problem with AppAuth if we change the code a bit).
When adding our SPM, and doing a build with the import we get an error:
Failed to build module 'navenioSDK' for importation due to the errors above; the textual interface may be broken by project issues or a compiler bug
... Library/Developer/Xcode/DerivedData/Sample-ebyeebvxavhdtqcthbulfduyrttt/Build/Products/Debug-iphonesimulator/navenioSDK.framework/Modules/navenioSDK.swiftmodule/arm64-apple-ios-simulator.private.swiftinterface:5:8 No such module 'AppAuthCore'
We are adding AppAuth and AppAuthCore to the app as a package dependency using AppAuth-iOS, but it appears not to be found.
Doing the same for AWS (the first on the list in arm64-apple-ios-simulator.private.swiftinterface) resolved fine, so it appears to be an AppAuth specific issue.
- Device: iPhone 11 / Simulator
- OS: iOS 16 target build on iOS 17.x
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the xcodebuild archive and import using the AppAuthCore package dependency, then inspect the generated navenioSDK.swiftmodule/arm64-apple-ios-simulator.private.swiftinterface mentioned in the report. Compare the failing AppAuthCore import with the AWS import that resolves successfully; done means the archived SDK imports successfully without the No such module error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100