[TIMOB-26721] iOS: Cannot deploy app extensions due to hardcoded Swift settings
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | cb-tooling |
| Reporter | Hans Knöchel |
| Assignee | Unknown |
| Created | 2019-01-13T17:28:43.000+0000 |
| Updated | 2020-01-30T23:09:17.000+0000 |
Description
[This PR](https://github.com/appcelerator/titanium_mobile/pull/8944) currently breaks iOS extension deployment: We are using an
Action Extension which is written in Swift. When deploying it, the build is rejected because of containing a Frameworks/ directory in the .appex bundle.
Inside it, the Swift standard libraries are added (because of [this line](https://github.com/appcelerator/titanium_mobile/pull/8944/files#diff-f430483233aa01af5b10df8390f9635dR3502)), which is invalid if your main target already contains Swift - like in our case.
The fix is to check if the main target already includes Swift and set the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES flag of the extension to NO. We currently hardcoded the value to be unblocked, but eventually a quick PR setting and checking the hasSwiftFiles for the main target.
No comments