Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the scenario where the main app uses the full AppAuth framework and a widget extension is in need of using AppAuth/Core, the frameworks imported through cocoapods will both be named AppAuth. This confuses the build-process, and leads to that both targets will be using the last imported framework. In order to be able to build with the described scenario, I have added a podspec for Core that will be treated as a separate framework, that one can import through cocoapods.
In the scenario where one does not have a requirement for the main-app to use the full framework and an extension to use the Core-only framework, one can still import core as AppAuth/Core in order to keep the framework name AppAuth.
With the added podspec, the separate core framework is called AppAuthCore.