The company I am working in is trying to develop our new mobile client side apps, for matters of "Develop once run an all", with the Appcelerator Titanium(SDk 1.7.5) iOS5 on a lion based Macs.
No one managed to work it out, so i'm a trying to figure this out during the weekend. I am getting the next build error (As a native developer for both IOS and Android I am used to work with the Xcode. From what i read in the site, i should build the app in the Titanium, not the XCODE??? the error when i am running form the Titanium, not the Xcode - the first unfamiliar item in my list....SHOULD I RUN IT IN THE TITANIUM OR THE XCODE FOR IOS?)
I can see that the build is starting and looking ok, if need all the log i will give it, but there are debug and info build lines and then i am getting this error and the build stops...
.
.
.
[ERROR]
[ERROR] Error: Traceback (most recent call last):
File "/Users/[USER]/Library/Application Support/Titanium/mobilesdk/osx/1.7.5/iphone/builder.py", line 1222, in main
execute_xcode("iphonesimulator%s" % link_version,["GCC_PREPROCESSOR_DEFINITIONS=LOG__ID=%s DEPLOYTYPE=development TI_DEVELOPMENT=1 DEBUG=1 TI_VERSION=%s %s" % (log_id,sdk_version,debugstr)],False)
File "/Users/[USER]/Library/Application Support/Titanium/mobilesdk/osx/1.7.5/iphone/builder.py", line 1140, in execute_xcode
output = run.run(args,False,False,o)
File "/Users/[USER]/Library/Application Support/Titanium/mobilesdk/osx/1.7.5/iphone/run.py", line 39, in run
sys.exit(rc)
SystemExit: 65
Other then that, I can the see that the engine in Python. Is it a problem with the python engine, the Titanium SDK or the the IOS SDK? When tried to run the "Hello world" app, we got more or less the same error.
Can any one help me with this issue? or send me to a good docs or tutorial to give me a direction?
Thank you,
Erez
my recommendation is to look in the build/iphone/build directory and open up the build.log to see what the real error is
Related
Hey I'm a newbie cocos 2d x developer, I'm just trying to get a "Hello World" project created in XCode for iOS. From the terminal I'm using the command
cmake ../.. -GXcode -DCMAKE_SYSTEM_NAME=iOS -DCMAKE_OSX_SYSROOT=iphoneos
I keep getting these two errors and the xcode project file does not generate.
CMake Error at cocos2d/cmake/Modules/CocosConfigDepend.cmake:94 (endmacro):
Flow control statements are not properly nested.
Call Stack (most recent call first):
cocos2d/cmake/Modules/CocosBuildSet.cmake:43 (include)
CMakeLists.txt:42 (include)
What am I doing wrong?
see attached screenshot
[1]: https://i.stack.imgur.com/cIiNC.jpg
System Specs:
MacOS Big Sur 11.4 (Virtual Machine via VMware)
cocos2d-x-4.0
cocos Console 2.3
Xcode 12.5.1
Python 2.7.16
cmake 3.21.0
CMake 3.14+
Xcode 10+
Visual Studio 2019
Android Studio 3.4+，NDK r19c+
Need https://github.com/leetal/ios-cmake
Try this
enter code here
$mkdir build_ios
$cd build_ios
$cmake .. -GXcode -DCMAKE_TOOLCHAIN_FILE=../ios.toolchain.cmake -DENABLE_ARC=FALSE
$open test.xcodeproj
The default is iOS device project, and platform parameters such as
os.toolchain.cmake support -DPLATFORM=SIMULATOR64 need to be added when adjusting to simulator. Please refer to its documentation
Under Xcode 8 symbolicatecrash to analyse crash report failed with:
sh: /Applications/Xcode.app/Contents/Developer/usr/bin/xcrun: No such file or directory
## Warning: can't find tool named 'otool' in iOS SDK, falling back to searching the Mac OS X SDK
sh: /Applications/Xcode.app/Contents/Developer/usr/bin/xcrun: No such file or directory
Error: can't find tool named 'otool' in the macosx SDK or any fallback SDKs at /usr/local/bin/symbolicatecrash line 115.
how to solve it?
Are you looking for the new location of symbolicatecrash in XCode 8?
Now it is located at /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources
find /Applications/Xcode.app/ -name symbolicatecrash
then, you will get
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
I recently updated to Xcode 7 and as usual something has to go wrong. Its really a shame because I was looking forward to the new features in Xcode 7.
I am faced with a an error which I cannot seem to fix. Every time I try and build the project I get the following error:
I thought there was something wrong with my project, so I made a new Single View application and I still get the same error.
I have tried the following things but none of them has worked for me:
Restart Xcode (Didn't work).
Clean and rebuild project (Didn't work).
Restart Mac (Didn't work).
Reinstall Xcode 7 from the Mac App Store (Didn't work).
Installed Xcode 7 on a different Mac (Still got the same issue, even with a new Xcode project).
I tried the solution in this Stack Overflow question: https://stackoverflow.com/a/31614717/1598906 - But alas it did not work.
Finally, I tried the following Terminal command with no avail: $ sudo killall -9 ibtoold
Is anyone else having this issue with Xcode 7.0? And if so, have you managed to come with any other solutions? I have tried everything I can think of and nothing works.
Lastly, below is a copy of the error Log:
2015-09-18 21:09:28.416 ibtoold[1598:39510] [MT] IBPlatformTool: ***
Failed to launch tool with description
System content
1x for IBCocoaTouchFramework-EightAndLater w/ default fidelity: Failed
to find or create execution context for description
System content
1x for IBCocoaTouchFramework-EightAndLater w/ default fidelity: Failed
to find a suitable device for the type SimDeviceType :
com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime :
9.0 (13A340) - com.apple.CoreSimulator.SimRuntime.iOS-9-0 (Failure reason: Failed to create SimDeviceSet at path
/Users/daniel/Library/Developer/Xcode/UserData/IB Support/Simulator
Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator
to see why creating the SimDeviceSet failed.) 2015-09-18 21:09:38.290
ibtoold[1598:39510] [MT] IBPlatformTool: Wrote failed marshalling
request diagnostics to path:
/var/folders/lx/kkhv57fd2ll7rhdt0bwfpkb00000gn/T/IB-agent-diagnostics_2015-09-18_21-09-28_418000
/* com.apple.ibtool.errors */ /Users/daniel/Desktop/DS
APPS/BT/BloodyTest/BloodyTest/Base.lproj/LaunchScreen.storyboard:
error: Could not open document
Recovery Suggestion: Failed to connect with the iOS agent. Please file a bug report at bugreport.apple.com and attach a zip file of the
diagnostics located at
"/var/folders/lx/kkhv57fd2ll7rhdt0bwfpkb00000gn/T/IB-agent-diagnostics_2015-09-18_21-09-28_418000".
Underlying Errors:
Description: Failed to find or create execution context for description
System content 1x for IBCocoaTouchFramework-EightAndLater w/ default
fidelity
Underlying Errors:
Description: Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with
runtime SimRuntime : 9.0 (13A340) -
com.apple.CoreSimulator.SimRuntime.iOS-9-0
Failure Reason: Failed to create SimDeviceSet at path /Users/daniel/Library/Developer/Xcode/UserData/IB Support/Simulator
Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator
to see why creating the SimDeviceSet failed.
Thanks for your time, Dan.
Well thanks to the community for all there help..... not.
In the end I got it working by simply upgrading to OS X El Capitan and Xcode 7.0.1.
One thing I would point out though, is that when I was looking through the Xcode app files, some of them were corrupted and when I updated to Xcode 7.0.1 this issue was not fixed. So before installing OS X El Capitan, I deleted the following:
Xcode 7.0.1 app
Library/Developer folder
Macintosh HD/Library/Developer folder
I then installed OS X El Capitan and then installed Xcode 7.0.1 and now everything works fine.
I hope this helps anyone else who is experiencing the same issue.
I'm running ....\bin\vsimporter.exe (with default settings) in my project folder and the .sln file seems to build successfully, but when I try running the simulator (on Win32 Solution Platforms, debug build), I get a bunch of errors. Most of the errors involve a missing file from the iOS 8.4 SDK (sys/types.h):
Error unknown argument: '-Xanalyzer'
Error 'sys/types.h' file not found
Error unknown type name 'XSym'
Am I supposed to include the iOS8.4 SDK? Any help/suggestions would be great.
I had the types.h problem too. Try to manually retarget to the Win 10 SDK:
Right-click on the solution and hit retarget, select the latest Win 10 SDK from the list, select all projects and click ok. The types.h problem should be gone.
Retarget answer worked for me to get rid of the errors with missing header files.
To get rid of the -Xanalyzer issue, I removed it from the .vcxproj file as a command line option using a text editor.
For the pods, I manually copied them from a Mac that already had them downloaded.
I have an app written using Titanium Mobile platform, and it works great on the simulator, but when I try to build for my device, it gives this error.
[INFO] Performing clean build
[ERROR]
[ERROR] Error: Traceback (most recent call last):
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.1/iphone/builder.py", line 1296, in main
execute_xcode("iphoneos%s" % iphone_version,args,False)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.1/iphone/builder.py", line 1057, in execute_xcode
output = run.run(args,False,False,o)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.1/iphone/run.py", line 39, in run
sys.exit(rc)
SystemExit: 1
Anyone got any idea what this error is about?
I got the same error when i tried to install my project to my device. I had used the following steps
Clean your project (Project -> Clean)
Close your Simulator
Restart your Titanium studio
Then Install the project to your device
Hope this helped you!!
As per comments...
That's not a very descriptive error, unfortunately. To get more
information on what's going wrong, can you open the Xcode project in
build/iphone, and try deploying to device from there? – Dawson Toth 23
hours ago
I did that - and found out the issue that way. I also found a log
file: build/iphone/build/build.log which probably would be more
revealing. Very bad error reporting from titanium, which really feels
like it is cobbled together with pritt stick and thumb tacks
sometimes. Turns out my error was with an expired key during the
codesign process - by the solution is to hunt down the meaningful
error message - whatever it may be. Thanks for the hint.
Try the following:
Make sure that if you are using localization files, there are no errors in those.
If you are using any kind of module, make sure that module is compatible with your SDK.
Clean your solution and then run the project again.
rest your Simulator
same question is asked here
No such file or directory : app.ap_