I am developing an app with trigger.io using some native plugins for iOS and i am having issues debugging my application.
The app is successfully transferred to the device, the app starts up and is suddenly terminated. The trigger io console output ends with:
[INFO] (lldb) connect
[INFO] Process 0 connected
[INFO] (lldb) waiting for connection event
[INFO] No connect event, assuming we are already connected
[INFO] (lldb) run
[INFO] error: process launch failed: failed to get the task for process 386
Here is a gist of the full output
My lldb version is lldb-320.4.124.10 .
Forge tools running at version 3.3.82, Xcode 6.0.2, the device is running iOS 8.0.2
Any hints are appreciated.
We've noticed that sometimes lldb & ios-deploy can get themselves into a hung state, especially if you have multiple forge run commands active.
To see if this is the issue here, try running:
lsof -i:12345
Try killing all processes listed and see if that helps.
This error also appears when you pick an ad-hoc or other production provisioning profile. Make sure that your code signing is for development.
Related
I have recently upgraded the Mac OS to Ventura 13.2.1 and Xcode to 14.2, now once I try to compile any application with Xcode, I am getting Kill:9 related issue for random task/framework in the project. I also get Kill:9 issue sometime on terminal as well.
Listing the errors here:
failed to read asset tags: The command `` terminated with uncaught signal 9. The command had no output.
Driver threw jobFailedWithNonzeroExitCode(9, "") without emitting errors.
Unable to execute command: Killed 9 Clang frontend command failed due to signal.
Please help me to resolve this issue/crash.
Open project in Xcode.
Build the app with Simulator (I tried with iPhone 14 Pro)
Error occurs in the build
Ideally project should have compiled without any error.
It sounds to me that the problem is with the installation of Xcode because when an unprivileged task is attempted, the OS will kill it off (with signal 9).
What I recommend is for you to re-install Xcode.
When you first run the new Xcode, it should prompt you for an administrator password in order to install system related components. Make sure you do this step. Hopefully that should then allow you to compile and run your iOS apps.
AppseleratorStudio (Titanium), build: 4.6.0.201605201934
MacBook Pro
iPad mini, OS 8.1.
Seen similar questions being asked, but not many answers were given and most of the questions were Android related. Willing to provide more info needed if necessary.
2016-08-22T08:48:24.385Z | DEBUG | getTiDefaultPath /Users/at/Library/Application Support/Titanium
2016-08-22T08:48:24.386Z | DEBUG | active sdk install path /Users/at/Library/Application Support/Titanium
2016-08-22T08:48:26.476Z | DEBUG | to download {"modules":[{"oses":["linux","win32","osx"],"platforms":["iphone","android"],"required":true,"partner_id":"A0B129A418829127EC551EB8ADB0D1CC","partner_name":"Appcelerator","name":"Hyperloop","description":"Gain complete access to native APIs in your Titanium mobile applications.","id":"hyperloop","guid":"99a136cd-4e51-40da-bcdb-d514f5895fb5","version":"1.2.6","url":"http://appcelerator-modules.s3.amazonaws.com/hyperloop-1.2.6.zip","min_mobilesdk_version":"5.4.0"}],"components":[]}
[ERROR] : Invalid "--device-id" value ""
Available iOS Devices:
814afcb29c793aea10b182b53f3f629b73ed1a39 iPad mini
itunes iTunes Sync
For help, run: titanium.js help build
Upd1. Added device id in build command, here is the result:
[INFO] Invoking xcodebuild
[ERROR] BUILD FAILED
[ERROR] The following build commands failed:
[ERROR] CodeSign build/Products/Debug-iphoneos/Anna-inzicht.app
[ERROR] (1 failure)
Also tried to clean project - no help.
Upd2. It works ok on emulator, fail is with real device only.
The simplest fix is to go to "Debug Configurations..." and delete the config for your project. Studio will automatically rebuild it or maybe ask you for which Provisioning Profile you want to use.
While Goltsev Eugene works it's a bit much, as creating a new project makes you loose all history, analytics, push, etc. on appcelerator platform.
Try adding --device-id 814afcb29c793aea10b182b53f3f629b73ed1a39 to your titanium build command.
Finally, the solution was easy - created new project, moved all files from app folder.Build works now.
For those still having this issue in 2019.
If you aren't able to locate your device in the device list, follow these simple steps.
Update NodeJS at https://nodejs.org/#download. Then rebuilding modules with by typing into the command-line: appc ti info -t ios.
You should see the following:
"You are attempting to run appc 7.1.0 which was compiled for node 8.9.1 but you are now running node v10.16.3
Rebuilding package modules ...
Package modules rebuilt!"
After that, my device popped up on my device list.
This took a while to figure out and I could not find this straight-forward solution anywhere.
Building Cordova app via Visual Studio using Remote build.
Was using Cordova version 5.3.1, tried updating to the latest version of Cordova too - 6.2.1-nightly.2016.5.23.6e87c71a.
Both times it works in Debug mode but does not work in Release Mode:
Errors - misleading and say nothing whatsoever:
http://imgur.com/TdSfuso
Part of the Output:
ERROR building one of the platforms : error : /Users/Jurgen/.taco_home/remote-builds/taco-remote/builds/66415/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 2
1> You may not have the required environment or OS to build this project (TaskId:10)
1> Failed to build app for buildNumber 66415: /Users/Jurgen/.taco_home/remote-builds/taco-remote/builds/66415/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 2 (TaskId:10)
1>22:57:03.377 1>
1>Error : Remote build error from the build server Build failed with error /Users/Jurgen/.taco_home/remote-builds/taco-remote/builds/66415/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 2: {1}
1> Done executing task "MdaVsCli" -- FAILED. (TaskId:10)
1>22:57:03.393 1>
1>Done building target "BuildMDA" in project "MobileAppNew.jsproj" -- FAILED.: (TargetId:11)
Full Output:
https://www.wetransfer.com/downloads/b9a4e2e932f98bb2286fbb6602c8dfc020160523210524/48dffd
We are planning to send the app to iOS to be released on the App Store but cannot do the .ipa file. Any help would be appreciated
How I solved this problem:
First of all I didn't manage to build and deploy on a device when using the App Store Production Certificate. I did manage however with the Ad hoc certificate, which is a production certificate with the only difference that you still have to specify the UDID of the devices you will deploy on in the developer account.
I then updated my Cordova version from 5.3.1 to 6.2.0. I updated 2 outdated plugins: Inappbrowser and Phonegap-plugin-push and voila; the app suddenly started to deploy in release mode (via a taco remote build). Weird bit is that I had been using the old version of cordova and never had to update the plugins when running in Debug mode - which was why it took me a bit more time to figure it out! Good luck :)
I am new with calabash-ios and have a dummy question is:
How possibly could I run a calabash test with real device which have installed ipa file (included calabash framework) and without xcodeproj?
Problem is I am doing QA and Dev only gives me ipa file to test without source code.
UPDATE:
I am able to run the ipa file in console and cucumber by adding BUNDLE_ID. And make sure the CFNetwork.framework is including in app framework to establish the connection.
But I got another problem to run the scenario:
1. When I run the command below:
DEVICE_ENDPOINT=http://192.168.1.9:37265 NO_LAUNCH=1 BUNDLE_ID=com.example.appname DEVICE_TARGET=UDID cucumber
Then I got this error:
A JSON text must at least contain two octets! (JSON::ParserError)
features/my_first.feature:8:in `Then I touch "LOG-IN/ CREATE ACCOUNT"'
all other steps was skipped
Then I run the console code
DEVICE_ENDPOINT=http://192.168.1.9:37265 NO_LAUNCH=1 BUNDLE_ID=com.example.appname DEVICE_TARGET=UDID calabash-ios console
Then I run server_version
I got reply back that said connection SUCCEED
But when I run start_test_server_in_background
It took me too long to wait and I see the app my physical device kept crashed and launch again and again until it stop as:
Unable to start. Make sure you've set APP_BUNDLE_PATH to a build supported by this simulator version
Calabash::Cucumber::Launcher::StartError: Calabash::Cucumber::Launcher::StartError:
"Timed out waiting for UIAutomation run-loop Error while writing to fifo. RunLoop::Fifo::NoReaderConfiguredError.
2015-10-01 10:49:41.634 instruments[15640:10558880] WebKit Threading Violation - initial use of WebKit from a secondary thread.
2015-10-01 10:49:42.574 instruments[15640:10558978] Attempting to change event horizon while disengage
2015-10-01 10:49:42.577 instruments[15640:10558877] Attempting to change event horizon while disengage
Instruments Trace Error : Target failed to run: Permission to debug app
Anyone can help please! I tried to search some solution but they almost issue on simulator and they contain xcodeproj. As a QA, I dont have the source code, only .ipa file. :(
Thanks
You should set 3 variables:
$ DEVICE_TARGET=<UDID> \
DEVICE_ENDPOINT=http://<ip>:37265 \
BUNDLE_ID=com.example.YourApp cucumber
The device and the host computer should be on the same network.
The .ipa must be installed on your device.
You can do this in Xcode by dragging-and-dropping in the Device Manager window or with a third-party tool like ideviceinstaller (available with homebrew).
You should never set NO_LAUNCH.
http://calabashapi.xamarin.com/ios/file.ENVIRONMENT_VARIABLES.html#label-NO_LAUNCH
You also need to enable you device for develop and turn on UIAutomation in the Settings.app > Developer.
Enabling device for development
RunLoop::Fifo::NoReaderConfiguredError
UPDATE In response to this question, I rewrote the Testing on Physical Devices Calabash iOS wiki page. Wow, that content was ancient!
As long as the file is build with calabash then that is not a problem. You just call cucumber with APP_BUNDLE_PATH to where ever your .ipa file is and should be all set.
But you should be aware that .ipa needs to be build to match the target you run the tests on.
I've setup my certificates correctly and it's not that. While trigger is copying everything to the device (I've tried one iPhone 4 with 5.1.1 AND an iPhone 4 with iOS6 beta 4) and it fails at 49%.
Line in console log: [ 49%] Copying PATH/development/ios/device-ios.app//tabs_modalWebViewController.nib to device
Going back in the console log, I find the following info if it helps any:
[ERROR] Failed when running /Users/joshmbrown/forge-workspace/fi-monuments/.lib/fruitstrap
ShellError: Failed when running PATH/.lib/fruitstrap
Any suggestions?
I've reinstalled Xcode and the proper command line utilities. I've also performed an xcode-select in the terminal. What else?