Sounds like an Xcode bug. If your Base SDK is 3.0, then you shouldn't
be able to select an Active SDK lower than 3.0, also, if your Active
SDK is iPhone Simulator 3.0, then the application should automatically
invoke a 3.0 simulator when you hit build-and-go.
Luke
On Jul 6, 2009, at 3:27
On 6-Jul-09, at 15:02 , Luke the Hiesterman wrote:
I noticed your crash report says
iPhone Simulator 3.0 (138), iPhone OS 2.2.1 (5H11)
That indicates that your simulator is actually running 2.2.1
software, where initWithStyle:reuseIdentifier doesn't exist, since
it became available in 3
On Jul 6, 2009, at 2:55 PM, Greg Parker wrote:
On Jul 6, 2009, at 2:27 PM, Luke the Hiesterman wrote:
On Jul 6, 2009, at 1:25 PM, DKJ wrote:
Any idea why the app is refusing to restart? This is what I get in
the Apple report:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x
On Jul 6, 2009, at 2:27 PM, Luke the Hiesterman wrote:
On Jul 6, 2009, at 1:25 PM, DKJ wrote:
Any idea why the app is refusing to restart? This is what I get in
the Apple report:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0002, 0x
Crashed Th
On Jul 6, 2009, at 1:25 PM, DKJ wrote:
Any idea why the app is refusing to restart? This is what I get in
the Apple report:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0002, 0x
Crashed Thread: 0
Application Specific Information:
iPhone
On 6-Jul-09, at 13:35 , David Duncan wrote:
Are you building with the 2.2.1 SDK and running on the iPhone OS 3
simulator? Perhaps the other way around? Either way, it is not a
supported configuration (the simulator OS must always match the SDK
used).
No, I'm using the 3.0 SDK.
__
On Jul 6, 2009, at 1:25 PM, DKJ wrote:
Application Specific Information:
iPhone Simulator 3.0 (138), iPhone OS 2.2.1 (5H11)
*** Terminating app due to uncaught exception
'NSInvalidArgumentException',
reason: '*** -[UITableViewCell initWithStyle:reuseIdentifier:]:
unrecognized selector
On 6-Jul-09, at 11:48 , DKJ wrote:
I'm getting an intermittent infinite loop in the simulator that I
can't seem to reproduce.
Both on the simulator and the device, the problem unfolds like this:
The app goes into its loop and begins filling up all available memory
with something or other.
On Jul 6, 2009, at 11:38 AM, DKJ wrote:
I want to terminate my UIApplication under some specific error
conditions. I'm used to doing this kind of thing using:
[[NSApplication sharedApplication] terminate];
But docs don't show a terminate method for UIApplication. Apparently
it will
On 6-Jul-09, at 11:40 , Luke the Hiesterman wrote:
Wanting to programmatically terminate an iPhone application is
typically indicative of a design flaw. On iPhone, only the user
decides when to exit an application. Why do you feel you need to
override the user here?
Good point. And as soon
Wanting to programmatically terminate an iPhone application is
typically indicative of a design flaw. On iPhone, only the user
decides when to exit an application. Why do you feel you need to
override the user here?
Luke
On Jul 6, 2009, at 11:38 AM, DKJ wrote:
I want to terminate my UIApp
I want to terminate my UIApplication under some specific error
conditions. I'm used to doing this kind of thing using:
[[NSApplication sharedApplication] terminate];
But docs don't show a terminate method for UIApplication. Apparently
it will respond to the message regardless; howeve
12 matches
Mail list logo
