[AC-6041] iOS:Hyperloop examples no longer builds
GitHub Issue | n/a |
Type | Bug |
Priority | n/a |
Status | Resolved |
Resolution | Cannot Reproduce |
Resolution Date | 2019-01-08T21:45:05.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Hyperloop |
Labels | n/a |
Reporter | Richard Lustemberg |
Assignee | Shak Hossain |
Created | 2018-11-29T09:40:28.000+0000 |
Updated | 2019-01-08T21:45:05.000+0000 |
Description
The hyperloop examples project no longer runs. When I attempt to build it, the build process exits while outputting the following:
{noformat}
Processing inherited protocols of WKURLSchemeTask
Iterating over inherited protocols of WKURLSchemeTask
Processing inherited protocols of NSObject
NSObject was already merged with all protocols it inherits from.
Merging NSObject => WKURLSchemeTask
Couldn't resolve typedef: ValueType
Not sure how to handle: name= value type= typedef value= ValueType
Not sure how to handle: name= simd_float3x3 type= record value= simd_float3x3
Couldn't resolve typedef: ObjectType
Not sure how to handle: name= firstObject type= typedef value= ObjectType
Couldn't resolve typedef: ObjectType
Not sure how to handle: name= firstObject type= typedef value= ObjectType
couldn't find class Protocol * {"name":"protocol","optional":false,"type":{"type":"objc_pointer","value":"Protocol *"}}
etc,etc
{noformat}
On the build logs you can see that the process quitted while generating stubs (build log 1).
If I try again, the build process will quit once more, with the following output:
{noformat}
[INFO] Forcing rebuild: Xcode project has changed since last build
[INFO] Finished Hyperloop assembly in 6.17 seconds
[INFO] Invoking xcodebuild
[ERROR] ** BUILD FAILED **
[ERROR] The following build commands failed:
[ERROR] Ld /Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/Hyperloop_Sample.app/Hyperloop_Sample normal x86_64
[ERROR] (1 failure)
{noformat}
In the build logs, it can be seen that the frameworks from the podfile have not been generated
{noformat}
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/CocoaAsyncSocket'
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/CocoaSSDP'
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/GLCalendarView'
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/JBChartView'
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/MMMarkdown'
[TRACE] ld: warning: directory not found for option '-F/Users/richard/Code/Hyperloop/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/Shimmer'
[TRACE] ld: framework not found CocoaAsyncSocket
{noformat}
I'll attach the build logs
Attachments
[~vijaysingh] can you test this too? I tried to reproduce it on my machine but the example project builds just fine. Tested with CocoaPods 1.5.3, Hyperloop 3.1.4 and SDK 7.4.1.GA
Hello, [~rlustemberg], [~jvennemann], I tried to reproduce the issue with SDK 7.5.0.GA with the sample project in https://github.com/appcelerator/hyperloop-examples . With CocoaPods 1.5.3, Hyperloop 3.1.3 I wasn't able to reproduce the issue. The projects run fine on iOS 12 simulator. Thanks.
I have two computers with the same issue, but I could not reproduce on a colleagues laptop. I wonder if it could be related to have had installed unix tools from brew long time ago (uninstalled already, because it installed its own version of 'cp' which had a different behaviour when copying recursively than the darwin version). AFAIK the CLI tools now should be the standard ones. The build process seems to quit silently while generating stubs. Is there a way to catch the error so that I can troubleshoot on my own?