[TIMOB-24057] Hyperloop: iOS - Adapt native CocoaPods build behavior
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2017-03-15T20:44:47.000+0000 |
| Affected Version/s | Hyperloop 2.0.0 |
| Fix Version/s | Hyperloop 2.0.1 |
| Components | Hyperloop, iOS |
| Labels | n/a |
| Reporter | Jan Vennemann |
| Assignee | Jan Vennemann |
| Created | 2016-10-20T16:54:34.000+0000 |
| Updated | 2017-03-15T20:44:53.000+0000 |
Description
*Current behavior*
The CocoaPods project is always built with the Release configuration and directly under
build directory.
*Expected behavior*
Same as when CocoaPods integrates itself into an Xcode project. The build output dir is the same as for the app. Also the Pods are built with the current build configuration.
This is required to integrate the two helper shell scripts that will copy resources and embed frameworks into the app's Xcode project.
Hyperloop PR (master): https://github.com/appcelerator/hyperloop.next/pull/96 Hyperloop PR (2_0_X): https://github.com/appcelerator/hyperloop.next/pull/97
Reopening due to issues with device builds. *Steps to reproduce the behavior* 1. Build the Hyperloop Example project for device 2. Run it and open one of the Third Party views *Actual behavior* The app crashes with a "Cannot find class XY" error *Expected behavior* The app should open Third Party views without crashing
PR (master): https://github.com/appcelerator/hyperloop.next/pull/123 PR (2_0_X): https://github.com/appcelerator/hyperloop.next/pull/124
Verified fixed using Hyperloop 2.0.1. Tested using the provided test case as well as multiple builds containing CocoaPods. Also tested TIMOB-23780 where the changes made in the PR are noticeable. No errors encountered.