[TIMOB-28143] iOS: modules hard-code path to TitaniumKit.xcframework in Xcode project from template
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2020-09-18T17:53:54.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 9.2.0 |
| Components | iOS |
| Labels | n/a |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2020-09-16T19:44:15.000+0000 |
| Updated | 2020-09-18T17:53:54.000+0000 |
Description
When a new module project is generated using a 9.2.0 SDK, the path to the TitaniumKit.xcframework folder is hard-coded to the absolute path inside the SDK used to generate the template.
We should be using a variable with a relative path so that when devs update the titanium.xcconfig to point at a different SDK install, the xcframework pointer also updates.
https://github.com/appcelerator/titanium_mobile/pull/12090
Verified the fix with SDK 9.2.0.v20200917131313.