Note that there are some explanatory texts on larger screens.

plurals
  1. POBug with starting Instruments via Profile under Xcode 4.1 Build 4B110
    primarykey
    data
    text
    <p><strong>Important Update</strong></p> <p>Strange bug is fixed (at least for me) in Xcode 4.2!</p> <hr> <p>I've a severe problem with Xcode 4.1 Build 4B110 under Mac OS X Lion and running Instruments via Xcode. The problem is that Instrument freezes in partly if I start it via Xcode. So if I start a project in Xcode 4.1 and open "Profile" the Instruments UI appears. The timer starts running, but the instruments app doesn't track anything and the more severe problem:</p> <p>The program seems to be running but does not react on any actions I make. So I can not click on any buttons etc. Nothing happens. The timer is still running, but I can not do anything. So I also can not close the window/app anymore. So I've to force stopping the Instruments app.</p> <p>But if I start the Instruments app directly via <code>Developer/Applications/Instruments.app</code> everything is ok. Of course the app doesn't track anything, but I can click on the buttons and anything possible there.</p> <p>So does anyone know about this problem? </p> <p>Does anybody know how to fix this weird problem?</p> <p>I've also deleted the developers folder with the corresponding deinstall-script file and reinstalled Xcode 4.1. But still the same problem.</p> <p>Can anybody give me a hint, tip, etc.?</p> <p>Would be really great!</p> <p><strong>Update</strong></p> <p>So, further weird stuff:</p> <p>Profile somehow worked for iOS 3.0 version apps, but after making a short break it didn't worked again. So I don't know where this bug is located. I guess it's about the target app iOS version.</p> <p>Thanks, Andreas</p>
    singulars
    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.
 

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