This repository has been archived by the owner on Jan 19, 2018. It is now read-only.
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.
Hi,
Actually it's impossible to compile a project with target using differents subspec.
for exemple,
TARGET A
pod atinternet-ios-objc-sdk
TARGET B (an AppExtension)
pod atinternet-ios-objc-sdk/AppExtension
=> compilation failed, conflict on frameworks names.
subspec are not the right solution to compile a light framework for AppExtension because it's final name is the same has the full one integrated to app.
A good solution ? (my pull request), is to use 2 podspecs to generate 2 frameworks with distinct names.
PS : The same issue exists on the Swift version. (but the same fix could fix it)