fix: mapping fails when bundle product name differs from target name #146
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.
Resolves issue raised here.
In Pods projects, the resource bundle added as a dependency uses the product name. However, the target name can be different such
Alamofire-iOS-Alamofirebundle's product name isAlamofire. When creating theprojectNativeTargetsmap, we use the product name as the key, so we don't throw here.Note this can cause a mismatch when the targets have a different name but the same product name. I couldn't figure out a good way to match the bundle product name with a specific target when there are multiple targets with the same product. I'd think this is quite rare outside of the Cocoapods context, so I'm leaning to living with that for now and reconsider this if it causes issues down the line.