I have jailbroken device ios version 5.0.1
When ever I try to debug my app on device the app exit with status 45.
I am using xcode 3.2.5 to debug. Is it not possible to debug on device os version higher than xcode sdk?
By the way here is the console log I got
unable to read unknown load command 0x25
unable to read unknown load command 0x26
Program loaded.
target remote-mobile /tmp/.XcodeGDBRemote-414-49
Switching to remote-macosx protocol
mem 0x1000 0x3fffffff cache
mem 0x40000000 0xffffffff none
mem 0x00000000 0x0fff none
run
Running…
[Switching to thread 7171]
[Switching to thread 7171]
sharedlibrary apply-load-rules all
continue
Debugger stopped.
Program exited with status value:45
No it isn't possible, this is most likely due to Xcode 3 not knowing how to handle your version of iOS. You'll either have to find a way to downgrade your device, or upgrade to Xcode 4.2 which supports iOS 5.0.1.
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.
Issue
Provision violated for watchdog scene-create: <FBSProcessResourceProvision: 0x282c3bc00; allowance: <; FBSProcessResourceAllowance; type: scheduledTime; timeValue: 0.40s>; violated: YES>
In my Nativescript-Angular app, older iOS devices like the iPhone6 fail to launch via pushkit because watchdog terminates it. I am not doing any network actions (which seems to be the main reason for watchdog from other posts).
I created a dummy app which have the same app module, app component and all I do is import the dependencies and I can still timeout. The time value fluctuates on every run and can range from 0.01s to the timeValue is 1.0s.
*On more recent devices like the iPhone8, X and iPads I do not encounter this issue.
Device & Nativescript Info
Nativescript Info:
✔ Component nativescript has 4.2.4 version and is up to date.
✔ Component tns-core-modules has 4.2.1 version and is up to date.
✔ Component tns-android has 4.2.0 version and is up to date.
✔ Component tns-ios has 4.2.0 version and is up to date.
Device: iPhone 6 using iOS 12
Built: Webpack with AOT and Uglify enabled + in production mode
I am curious to see if others have run into this issue or if anyone has any suggestions as to how I can improve the launch time and avoid the watchdog timeout.
I have a problems when I want to run my application on my iPhone in Xcode 9 and using Swift lang.
When I run this application in simulator everything is all right, but when I connect my iPhone (by cable or wireless) to my MBP I have an error:
Swift stdlib tool Error: Task failed with exit 1 signal 0
and application stopped.
Why I have this error message and how can I test my app on my devices?
Thanks for all answers.
P.S.: Xcode 9.2 (9C40b) iOS 11.2 (Deployment target)
If removing DerivedData don't help try to just reboot phone or mac.
It mainly works for me with that error
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.
When I call GDB on my iPhone to 'dump memory X.bin #x#### #x####' the .bin file is empty (1.6 MB of nothing). I have tried a few different ways to attach to the app and dump it, but every time the .bin is empty. This is also the case if I run the app in the simulator and try to dump from Xcode.
I have an iPhone 4 (jailbroken) with iOS 5.0.1 with SDK 5.1 (Xcode bundle 4.4.1) and GDB version 6.3.50-20050815 (Apple version gdb-1708 + reverse.put.as patches v0.4).
Any ideas? Any suggested alternatives to GDB?
You should disable ASLR by changing the MH_PIE flag on the Mach-O header.