Note that there are some explanatory texts on larger screens.

plurals
  1. POLaunching app with iOS instruments is unreliable
    primarykey
    data
    text
    <p>I launch my iOS app on the device (not simulator) with the following command (app is already installed).</p> <pre><code>instruments \ -w c717fa22472d7b691ae5763af90e1e44244ad85a \ -t /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate \ -D "/Users/mj/Desktop/apps/trace" \ LPSimpleExample-cal \ -e UIARESULTSPATH /Users/mj/Desktop/apps \ -e UIASCRIPT /Users/mj/Desktop/apps/_run_loop.js </code></pre> <p>6 out of 10 times it is working. In case of an error I get the following message:</p> <pre><code>2013-10-07 16:45:51.553 instruments[9891:1207] unable to locate CFBundleIdentifier for path: LPSimpleExample-cal 2013-10-07 16:45:51.555 instruments[9891:1207] Recording cancelled : At least one target failed to launch; aborting run Instruments Trace Error : Error Domain=com.apple.instruments Code=1 "Error Starting Recording" UserInfo=0x7faccbef8fa0 {NSLocalizedDescription=Error Starting Recording, NSLocalizedRecoverySuggestion=At least one target failed to launch; aborting run} Instruments Trace Error : Failed to start trace. </code></pre> <p><br> For me it looks that instruments has a bug here. I tried to launch the app over 100 times, in different scenarios and I can't analyze an error pattern. The device crashlog says:</p> <pre><code>Process: DTMobileIS [34956] Path: /Developer/Library/Daemons/DTMobileIS Identifier: DTMobileIS Version: ??? (???) Code Type: ARM (Native) Parent Process: lockbot [34938] Date/Time: 2013-10-07 15:29:05.474 -0700 OS Version: iOS 6.1.3 (10B329) Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000 </code></pre> <p>Exception type <code>EXC_BAD_ACCESS (SIGSEGV)</code> indicates that an object which is getting accessed has been already released. A <code>SIGSEGV</code> is a segmentation fault, meaning you it is trying to access an invalid memory address. Reference: <a href="https://stackoverflow.com/questions/7446655/exception-types-in-ios-crash-logs">Exception Types in iOS crash logs</a></p> <p>Instead of using the bundleIdentifier I also tried to specify the full app path or the full bundleIdentifier:</p> <pre><code># with full app path instruments \ -w c717fa22472d7b691ae5763af90e1e44244ad85a \ -t /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate \ -D "/Users/mj/Desktop/apps/trace" \ /Users/mj/Desktop/apps/LPSimpleExample-cal.app \ -e UIARESULTSPATH /Users/mj/Desktop/apps \ -e UIASCRIPT /Users/mj/Desktop/apps/_run_loop.js # with full bundleIdentifier instruments \ -w c717fa22472d7b691ae5763af90e1e44244ad85a \ -t /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate \ -D "/Users/mj/Desktop/apps/trace" \ /Users/mj/Desktop/apps/LPSimpleExample-cal.app \ -e UIARESULTSPATH /Users/mj/Desktop/apps \ -e UIASCRIPT /Users/mj/Desktop/apps/_run_loop.js </code></pre> <p><strong>Configuration details</strong></p> <ul> <li>Instruments version: 5.0 (51166)</li> <li>XCode version: 5.0 (5A1413)</li> <li>Device Types: iPhone 5 - 6.1.3, iPhone 5C - 7.02, iPhone 5S - 7.0.2</li> </ul> <p>Has anyone more information in which cases instruments can't launch an app on the device or when do you receive the error message <code>unable to locate CFBundleIdentifier for path: LPSimpleExample-cal</code>?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload