I've begun testing my iOS app on my iPhone. Everything works great for a week or so and then my app starts to crash immediately when I try to open it. When I check the logs for my phone (Window-Devices-Select my iPhone), I see the following log messages.
<Notice>: Submitted job with label: UIKitApplication:com.app.App-Name[0x9fed][63]
<Notice>: /private/var/containers/Bundle/Application/64152E86-B292-47E5-A12D-27E5E23CACFF/App-Name.app/App-Name not valid: 0xe8008015: A valid provisioning profile for this executable was not found.
<Error>: Unable to obtain a task name port right for pid 14847: (os/kern) failure (0x5)
May 29 08:46:13 iPhone assertiond[63] <Notice>: Failed to start job
with error Error Domain=NSPOSIXErrorDomain Code=3 "No such process"
UserInfo={NSLocalizedRecoverySuggestion=Consult
/var/log/com.apple.xpc.launchd/launchd.log for more information,
NSLocalizedDescription=Unable to get valid task name port right for pid
14847, NSLocalizedFailureReason=The process failed to exec}
<Notice>: Deleted job with label: UIKitApplication:com.app.App-
Name[0x9fed][63]
<Notice>: [app.App-Name] Bootstrap failed with error: <NSError:
0x115657730; domain: BKSProcessErrorDomain; code: 1 (bootstrap-failed);
reason: "Failed to start job">
<Error>: Bootstrapping failed for <FBApplicationProcess: 0x11d2702a0;
com.app.App-Name; pid: -1> with error: Error
Domain=BKSProcessErrorDomain Code=1 "Unable to bootstrap process with
bundleID com.app.App-Name" UserInfo={BKSProcessExitReason=0,
NSLocalizedFailureReason=Failed to start job,
NSUnderlyingError=0x11fa53590 {Error Domain=NSPOSIXErrorDomain Code=3
"No such process" UserInfo={NSLocalizedFailureReason=The process failed
to exec, NSLocalizedRecoverySuggestion=Consult
/var/log/com.apple.xpc.launchd/launchd.log for more information,
NSLocalizedDescription=Unable to get valid task name port right for pid
14847}}, BSErrorCodeDescription=bootstrap-failed,
NSLocalizedDescription=Unable to bootstrap process with bundleID
com.app.App-Name}
<Notice>: <FBApplicationProcess: 0x11d2702a0; com.app.App-Name; pid: -1> exited.
<Notice>: SystemUI unknown identifier: 'com.app.App-Name'
<Notice>: Process exited: <FBApplicationProcess: 0x11d2702a0; com.app.App-Name; pid: -1> -> <FBApplicationProcessExitContext: 0x176235aa0; exitReason: (none); terminationReason: (none)>
I've googled for these error logs to try and find a solution, but no luck.
Any help would be much appreciated.
Connect your iOS to your computer with a USB or Lightning cable. Go to Window > Devices and select your device from the list. Click the "up" triangle at the bottom left of the right hand panel. All logs from all apps on the device will be displayed here.
If you encounter a crash while debugging your app using Xcode, the debugger intercepts the crash so you can inspect your app’s state. If you’d like to gather the full crash report for the issue, detach the debugger, either by using the Debug > Detach menu item in Xcode, or by issuing the detach command in the debugging console.
You can view these logs using the Devices and Simulators window in Xcode, described in About Devices and Simulators window. If a customer reports a crash, they can transfer the crash report to either a Mac or Windows computer. See Find device crash and energy logs on a Mac or Windows computer.
Use crash reports and device logs to debug app issues. Customers expect apps to be stable, free of bugs, and use system resources efficently. The operating system helps you meet these expectations by collecting different log types you can use to diagnose issues in your app:
On iOS, there are two types of logs: console logs and crash logs. Console logs are displayed in the console log history and are records of some system events that are updated in realtime. A crash log is a log file that is created after an emergency shutdown of the application (Crash). The crash log file has the resolution .crash or .ips.
I had the same situation with an app which Bundle Identifier has been moved to another Apple Developer Team.
After Bundle Identifier was moved, a previous build was containing a provisioning profile which was no longer valid, and I got this error message in logs.
I guess the same happens if you delete the Provisioning Profile or if it is invalidated for whatever reason.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With