PDA

View Full Version : Anyone else having stability issues with iPhone SDK beta 2?




darkpaw
Mar 30, 2008, 10:26 AM
I installed Xcode 3.1 and the iPhone SDK beta 1 when it was released. I had no problems with it.

Apple released beta 2 the other day and I installed that over the top of the previous install.

Since then - on both a new 2.8GHz 8-core Mac Pro (Early 2008) and a 2.6GHz C2D 17" MBP SR (Nov 2007) - the iPhone simulator will sometimes fail to launch.

When this happens, GDB (the debugger) says it failed to launch the simulator, then I'll be unable to launch ANY application as I get a -10810 error from the Finder. Applications already running continue to run but I can't start any new processes.

Once that happens, it's about 20 seconds before everything disappears and I'm thrown back to the login screen.

No other software has been installed on these machines other than whatever security updates Apple released, and the new firmware for the Mac Pro. (Given that this is seen on the MBP as well, the firmware cannot have been the cause.)

Any ideas?

Here's what the Console says:
30/03/2008 15:57:29 [0x0-0x2a02a].com.apple.Xcode[502] Xcode(502,0xb0103000) malloc: free_garbage: garbage ptr = 0x37f08f0, has non-zero refcount = 1
30/03/2008 15:57:56 Xcode[502] !!! _NSGlyphTreeInsertGlyphs invalid char index
30/03/2008 15:57:56 Xcode[502] !!! _NSGlyphTreeSetIntAttributeForGlyphAtIndex invalid glyph index 54471

I'm definitely freeing memory as and when necessary, but I can't see how that might crash the entire system?!



digitoxin
Mar 30, 2008, 08:10 PM
ditto, same problem for me, and this is after a fresh OS install.

i can open the simulator if my code isn't buggy, but after a few times of my app crashing Aspen, Aspen will fail to load, and the whole OS crashes.

I'm running a mac mini 1.66GHz core duo, 2GB RAM with OS 10.5.2

darkpaw
Mar 31, 2008, 06:51 AM
...after a few times of my app crashing Aspen, Aspen will fail to load, and the whole OS crashes.

I'm running a mac mini 1.66GHz core duo, 2GB RAM with OS 10.5.2
Are you using beta 1 or 2 of the SDK? Apple renamed the Aspen Simulator to iPhone Simulator in beta 2.

Glad (if that's the right word) to see it's not just me experiencing this annoyingly serious error.

Every time it crashes, I send the crash report to Apple. Hopefully, someone's going to pull their finger out and fix this.

bretzie
Mar 31, 2008, 11:15 AM
I am getting this exact same issue on my MacBook Pro regularly. Frustrating...

darkpaw
Mar 31, 2008, 01:27 PM
I think something is changing permissions when this happens. This might explain why we can't launch applications afterwards.

When the iPhone Simulator fails to launch, this is the start of it. At that point, there are loads of those messages in the Console.

If iTunes is playing something at the time, and you quit Xcode, the Finder will throw you out to the login screen, but iTunes is still playing your music.

When you login again, iTunes cannot load the library because it's locked by another user or process.

I let Disk Utility repair permissions - something I had done last night, too. This time though, the following appeared:
Repairing permissions for "X"
Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/frontline.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/frontline.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_large.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_large.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_medium.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_medium.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_medium_simple.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_medium_simple.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_small.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_small.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_small_simple.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/indicator_small_simple.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left1.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left1.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left2.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left2.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left3.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left3.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left4.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left4.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left5.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/left5.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/openinfinder.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/openinfinder.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileArrow.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileArrow.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileLeftArrow.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileLeftArrow.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileRightArrow.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/pileRightArrow.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/poof.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/poof.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/resizecursor.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/resizecursor.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/resizecursorv.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/resizecursorv.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right1.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right1.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right2.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right2.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right3.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right3.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right4.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right4.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right5.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/right5.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-l.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-l.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-m.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-m.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-sm.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-sm.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-xl.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/scurve-xl.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separator.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separator.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separatorstraight-horizontal.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separatorstraight-horizontal.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separatorstraight.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/separatorstraight.png", should be 0, group is 20.
User differs on "System/Library/CoreServices/Dock.app/Contents/Resources/shadow.png", should be 0, user is 501.
Group differs on "System/Library/CoreServices/Dock.app/Contents/Resources/shadow.png", should be 0, group is 20.
Group differs on "Library/PreferencePanes", should be 0, group is 80.
Permissions differ on "Library/PreferencePanes", should be drwxr-xr-x , they are drwxrwxr-x .
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/jvm.cfg", should be 0, user is 95.
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/classlist", should be 0, user is 95.
Group differs on "Library/Widgets", should be 0, group is 80.
Permissions differ on "Library/Widgets", should be drwxr-xr-x , they are drwxrwxr-x .
ACL found but not expected on "Library".

Permissions repair complete

This doesn't fix it, as I still have to reboot to do anything useful. I've submitted this to Apple.

pwnerer
Mar 31, 2008, 02:17 PM
I've had this issue as well - it started after Beta 2 and for me it seems to happen if you leave the simulator running and you try and run the app again.

This is really annoying, I've had to restart my machine many times today :mad:

digitoxin
Mar 31, 2008, 11:13 PM
Are you using beta 1 or 2 of the SDK? Apple renamed the Aspen Simulator to iPhone Simulator in beta 2.


Sorry I meant Iphone Simulator. I'm running Beta 2.

darkpaw
Apr 1, 2008, 07:00 AM
So it looks like iPhone SDK beta 2 is 'a bit dodgy'.

I ask you all to report this to Apple via their feedback page here: http://www.apple.com/feedback/macosx.html/

In the meantime, tonight, I'll uninstall Xcode 3.1 and the SDK, and install it in a new location from scratch and see if that works.

csimoes
Apr 1, 2008, 07:20 AM
I also installed the XCode 3.1 iPhone SDK update 2 (9A2151) on top of the original iPhone SDK, and ever since using XCode and the IPhone Simulator will cause my computer to lock up. It feels like Apple tried to rush out the interface builder, and didn't test this release enough. I am going to uninstall XCode all together and revert back to the original iPhone SDK, which I fortunatly still have.

ElNono
Apr 1, 2008, 08:37 AM
I had that problem once with Beta 1, but with Beta 2 it's more pronounced.
I noticed that when it happens, I can press the power key on the keyboard (the one that brings the Shutdown/Restart/Sleep dialog), and it will cause the Finder to restart and then I can launch apps again.
As far as I've been able to tell, it's launchd that's crashing and killing the system.

In other news, [NSUserDefaults] seems broken on this Beta 2 release. Anybody else noticed this too?

reformist
Apr 2, 2008, 03:31 AM
I had this problem all day today, and I think I've learned a few things about it. In my case, my iphone app was crashing the simulator. I was trying to debug it, so I had a frequent launch->crash cycle from within xcode. About 4 or 5 times after I'd launch the app and simulator, the simulator would fail to open.

If you have a terminal open when this happens, you can ls -alh and see that your files are not identified by the username, but instead by the user ID - usually 501 or 50x. You can't sudo -s, you can't ssh, you can't do jack. If you try to open system preferences and the like, you'll get a -10810 error.

It's as if OSX has lost your user information. What I think is happening is that the iphone simulator is crashing lookupd, which is responsible in OSX for name resolution of both internet addresses and usernames from IDs. The error is crippling: I don't think it's possible to restart lookupd without logging out and logging back in or doing a restart.

I suspected it might be my computer, but I was able to reproduce it in 10 minutes on a fresh macbook air with just the sdk installed. It's an awful, awful bug. I hope a fix is imminent.

mysticwhiskey
Apr 2, 2008, 06:36 AM
I had this problem all day today, and I think I've learned a few things about it. In my case, my iphone app was crashing the simulator. I was trying to debug it, so I had a frequent launch->crash cycle from within xcode. About 4 or 5 times after I'd launch the app and simulator, the simulator would fail to open.

I get the SDK crash too, where everything shuts down - reformist's situation sounds identical to mine.

yayaba
Apr 3, 2008, 12:39 AM
Ugh, I thought I was the only one with this problem! I even posted in the main OSX forum. The problem drives me absolutely nuts when it happens.

So far today it's ok but a few days ago I was getting it after like a minute of using the simulator. I hope Apple fixes this soon... it makes programming almost impossible.

johnellisdm
Apr 3, 2008, 12:48 AM
i have had the problem as well...

i have noticed that if you log out as soon as you get the "simulator failed to start" message, then you can keep going without a restart. the weird thing is that the OS leaves all your stuff running as background? processes or something. for instance, i can see "firefox-bin" in the process list and firefox won't start until i kill that process.

yayaba
Apr 3, 2008, 12:58 AM
i have had the problem as well...

i have noticed that if you log out as soon as you get the "simulator failed to start" message, then you can keep going without a restart. the weird thing is that the OS leaves all your stuff running as background? processes or something. for instance, i can see "firefox-bin" in the process list and firefox won't start until i kill that process.

That's what I do sometimes to make it better but I think if you do your system will be in a half messed up state. I start up Xcode and start coding again but I'll see it happen like 2 minutes later.

H3rbz
Apr 3, 2008, 09:15 AM
I'm experiencing this too sometimes, but what really frustrates me (and what I think might be related) is that using [NSUserDefaults standardUserDefaults] does not seem to access the simulators defaults, but rather my Macbook Pro's defaults.

This not only prevents me from testing Settings application extensions, but it might very well mess up my local user account's preferences.

Anyone have any thoughts on this? Am I doing something wrong when using NSUserDefaults or is the IDE/SDK to blame?

ElNono
Apr 3, 2008, 09:35 AM
I'm experiencing this too sometimes, but what really frustrates me (and what I think might be related) is that using [NSUserDefaults standardUserDefaults] does not seem to access the simulators defaults, but rather my Macbook Pro's defaults.

This not only prevents me from testing Settings application extensions, but it might very well mess up my local user account's preferences.

Anyone have any thoughts on this? Am I doing something wrong when using NSUserDefaults or is the IDE/SDK to blame?

This is what I noticed with NSUserDefaults:
1) In the Beta 1 SDK, the preferences used to be stored in ~/Library/Application Support/Aspen Simulator/User/Library/Preferences
2) In the Beta 2 SDK, each application has it's own storage. The files are available at: ~/Library/Application Support/iPhone Simulator/User/Applications/<The App UUID>/Library/Preferences
3) When you launch the Simulator from XCode, it uses a sandboxed environment (man sandbox), and that seems to be the culprit of why the NSUserDefaults are not loaded in that case. The NSUserDefaults do get saved and reloaded just as long as you don't quit the Simulator or relaunch your app from XCode. This basically makes NSUserDefaults testing useless.
4) When you launch the Simulator standalone, by double-clicking it, it is not sandboxed, and NSUserDefaults work as expected, even between Simulator sessions.

So there must be a bug somewhere with their sandboxing that's screwing up the NSUserDefaults loading while under XCode.

H3rbz
Apr 3, 2008, 10:02 AM
Thx ElNono, but ...

I'm not seeing any difference when launching the simulator directly. I did find out that my prefs are still found in: ~/Library/Application Support/iPhone Simulator/User/Library/Preferences and are indeed updated when using the Settings application. The application specific prefs dir is empty. If the Settings application is using the global prefs dir and the application is using it's own location, then the behavior I see would be explained and there is just a logic error in the environment.

I think I'm gonna start a fresh project, just to make sure the SDK+simulator updates, while working on the project, are not causing such conflicts. It makes sense that I don't get to my application's prefs, when there are none in the expected location.

The method I'm using to test this, btw, is by printing out the dictionaryRepresentation of the defaults and looking for my application specific keys...

steve1717
Apr 3, 2008, 04:54 PM
Using Beta 1, my Xcode keeps crashing (not the simulator) and the console cites:

4/3/08 2:44:23 PM Xcode[671] !!! _NSGlyphTreeSetIntAttributeForGlyphAtIndex invalid glyph index 85435

several times until:

4/3/08 2:44:23 PM Xcode[671] !!! Suppressing further NSGlyphTree logs

at that point I get the spinning beachball and am forced to Force-Quit Xcode.

mbpc2d.user
Apr 4, 2008, 09:43 AM
I'm having a problem I have not seen mentioned anywhere, I cannot get past the methods of classes, meaning if I try to change the background color of a view through initWithFrame I only get to self.b for self.backgroundColor then Xcode completely crashes, no warning or error codes of any sort. I thought maybe there is a code sense problem, but turning code sense off didn't help. So there's a new problem with the SDK, I'd report it to Apple, but I wouldn't know what to tell them.

brdgolf1
Apr 4, 2008, 12:19 PM
I am also getting the Beta 2 crashes as well. However I do not wait for it to return nor do I restart the computer. All I need to do is logout and log back in and the problem goes away until the next time.

mbpc2d.user
Apr 4, 2008, 02:30 PM
Now I am just getting frustrated, I haven't made any progress in the last 5 hours, Xcode keeps crashing and I keep losing code. I am totally bummed.

GregX
Apr 4, 2008, 04:50 PM
Same problem as everyone else, last week when I downloaded it It was driving me crazy. Run the simulator change some code re-run, was getting about 2 attempts before it would crash forcing me to restart the finder.

After about 1 hour I was doing my nut. Couple of times it completely froze my MBP and I had to turn off with the power button.

Beta 1 was really good for me, no issues - almost wish I'd kept the installer as this is driving me crazy.

Anyway after a little craziness I changed a few settings in XCOde and managed to get some stability, though I still get the same problems, however they are markedly less. Can now get about 30 minutes work done before each restart. It's not perfect but I guess this is beta for you :)

In Xcode the project settings (General) the base sdk was pointing at Device - IPhone SDK. After switching to the Simulator IPhone OS 2.0 it settled down a bit.

I don't know if this helps anyone but it made the beta 2 a little more usable.

Come on Apple sort it out, this is way below your usual standard.:apple:

maxjg
Apr 5, 2008, 07:47 PM
Add one more to the count. The needs to be fixed, right away. Getting tired of rebooting because of it.

yayaba
Apr 5, 2008, 08:28 PM
Now I am just getting frustrated, I haven't made any progress in the last 5 hours, Xcode keeps crashing and I keep losing code. I am totally bummed.

I ran into some problems where I would type code and Xcode crashes. I got around it by typing jargon around the code, then deleting the jargon leaving just my code.

jtbandes
Apr 6, 2008, 12:21 AM
Yep, I'm having the same issue. This seriously hinders productivity. They need to fix this.

t4cgirl
Apr 6, 2008, 12:40 AM
MacBook Air, fully patched 5.2. Same issue

Cromulent
Apr 6, 2008, 05:16 AM
Bug report it to Apple if you are having problems.

You are using beta software, there will be problems whether that is to do with stability or just general usability. That is the price you pay for getting a head start.

paintballer
Apr 6, 2008, 05:57 PM
I'm having the same issues...I feel like I'm using a MS product... :eek:

yayaba
Apr 6, 2008, 08:52 PM
I'm having the same issues...I feel like I'm using a MS product... :eek:

To be fair i've never had this bad of a problem with a MS product. But also to be fair again, this is Beta and the MS products I use (Office, Visual Studio) are release candidates.

Still wish Apple could hot fix this instead of waiting for Beta 3 to fix this however long that will take. This is a pretty damn bad bug. I just finished restarting my machine :mad:

DrummerB
Apr 7, 2008, 04:36 PM
Same problem, too. And I have nothing else installed on my new Mac mini than the SDK.
Beside the crashing issue, did anyone had a problem with breakpoints? The debugger doesn't stop at any breakpoints I set anymore. I don't know if this adheres with the crashing problem.
I think I'll reinstall SDK version 1.

Sbrocket
Apr 7, 2008, 04:59 PM
Apple doesn't know to fix it if you don't file a bug report so engineering can track it.

http://bugreporter.apple.com/

Cromulent
Apr 7, 2008, 05:02 PM
Apple doesn't know to fix it if you don't file a bug report so engineering can track it.

http://bugreporter.apple.com/

Exactly. If it is such a nuisance then send Apple a bug report. If you can't be bothered to do that then stop moaning.

Edit : Just saw your avatar for the first time. Hahaha.

Sbrocket
Apr 7, 2008, 05:08 PM
Yeah, I've had it for a while now...its such a good avatar. :cool:

Make sure you follow the Bug Reporter Guidelines before you submit the bug, too, or engineering will toss it aside. Good syntax is nearly as important in bug reports as it is in coding. If more than one of you wants to file concurrent reports, that's good too...they'll get marked duplicates, but bugs tend to get bumped to the top of the list based on reported volume.

mysticwhiskey
Apr 7, 2008, 09:29 PM
Same problem, too. And I have nothing else installed on my new Mac mini than the SDK.
Beside the crashing issue, did anyone had a problem with breakpoints? The debugger doesn't stop at any breakpoints I set anymore. I don't know if this adheres with the crashing problem.
I think I'll reinstall SDK version 1.

I get the breakpoint problem intermittently, although a reboot tends to fix it up.

jtbandes
Apr 7, 2008, 11:04 PM
I've got a bug filed and they requested more information, which I just sent. We'll see how this goes. Hopefully they can get a fix out sometime soon... (somehow I can just see this being some engineer's idea of a late april fool's joke :P)

GregX
Apr 8, 2008, 12:21 PM
All,

Yes it is a beta product and yes we are all ready to accept issues with beta products, this is indeed the problem with being on the cutting edge. However this really is such a big issue that it's hard to believe it could have been released with such glaring problems.

I am a software developer and I would never excuse myself or any of my team for releasing such a big issue, beta or not. It stinks of rushed out.

Nuff said.

Anyway I am not just "Moaning" I have also raised a bug with apple and await a fix for something that is causing major headaches for many.

People are posting because they can't believe that this kind of error can not be down to something they have done.

This thread is to let people know there are issues with Beta 2 and people are free to raise and question, this is what forums are for.

Regards

Greg X:eek:

DrummerB
Apr 8, 2008, 12:41 PM
I get the breakpoint problem intermittently, although a reboot tends to fix it up.

Yes, it's very stange. Both, the breakpoint and the crashing problems seemes to come and go. :confused:

I wanted to report this bug, but I didn't find the bug report site. And now, that I reinstalled OS X and XCode, I can't reproduce the bug anymore.

maxjg
Apr 8, 2008, 04:54 PM
Yes, it's very stange. Both, the breakpoint and the crashing problems seemes to come and go. :confused:

I wanted to report this bug, but I didn't find the bug report site. And now, that I reinstalled OS X and XCode, I can't reproduce the bug anymore.

Pleeeeeease be fixed in Beta 3 (Downloading)

GregX
Apr 8, 2008, 04:56 PM
All,

Well lets hope beta 3 solves the problem. Downloading it now so I hope to god this issue has gone away and we can get on and write code without constant reboots.

:cool:

darkpaw
Apr 8, 2008, 05:44 PM
As the thread starter, I have vented my spleen at Apple a good twenty times in the past couple of weeks. This is the worst software to have come out of Apple in a long time.

I even emailed Steve Jobs telling him that this software had stopped my development of an iPhone/iPod game for two weeks because of this bug, and I'm finding it hard to get back into it, even with the third beta of the SDK.

I guess I'll get back into it, but if I come across another bug (that really should NOT have got through their testing (did they do any?)) like this, I'm likely to pause development again.

yayaba
Apr 8, 2008, 06:20 PM
As the thread starter, I have vented my spleen at Apple a good twenty times in the past couple of weeks. This is the worst software to have come out of Apple in a long time.

I even emailed Steve Jobs telling him that this software had stopped my development of an iPhone/iPod game for two weeks because of this bug, and I'm finding it hard to get back into it, even with the third beta of the SDK.

I guess I'll get back into it, but if I come across another bug (that really should NOT have got through their testing (did they do any?)) like this, I'm likely to pause development again.

I still went on programming the past two weeks but it was pretty hellish. I think I've restarted my Macbook more in the past two weeks than I have the past year.

Let me know if Beta 3 fixes the problems. I won't have a chance to test it out until later on tonight.

pwnerer
Apr 8, 2008, 06:23 PM
Any luck with Beta 3? I've rolled back to Beta 1 so I could continue working, but curious if Beta 3 has fixed the main issue (apps fail to start).

Korolen
Apr 9, 2008, 02:07 AM
My Beta 3 just crashed.

I love Apple.

jtbandes
Apr 9, 2008, 11:48 PM
Yep, beta 3 has the same issue. No fixy. :mad:

Hopefully Apple looks at my bug (or anyone's) and fixes it.

GregX
Apr 11, 2008, 12:51 PM
All,

Yep I have now seen the same issues that we have all had before under Beta 3, although I do think that it happens less often (still not convinced). It's good to see they have added more elements to Interface Builder as that is clearly more important than pissing developers off by having to reboot 200 times a day when using the software - good job Apple...

What exactly was the point of release Beta 3 so soon after Beta 2 if it didn't fix the most serious error of all - I would have fired someone by now ! Very POOR
:mad:

Sbrocket
Apr 11, 2008, 01:27 PM
I dunno what you guys are talking about. Unless the SDK Betas are somehow responsible for my logic board frying itself within a year of purchasing my MBP (grrr!), I've had no major problems out of it that I didn't expect. The device's error handling capabilities if you don't implement some exception catching still is a bit cruddy, but that's really my only complaint so far (other than the unstable, as in changing, API but that's also expected at this stage).

:confused::confused:

csimoes
Apr 17, 2008, 10:20 PM
I was having lots of trouble with the iPhone SDK Beta 2 where ti would crash all the time. I have been using the iPhone SDK Beta 3 for the last few days, and it has not crashed at all. For my machine it is much more stable.

-Chris

Sbrocket
Apr 18, 2008, 12:35 AM
Since that post a week ago I have run into the -10810 error you guys were talking about multiple times. Only thing I can recommend is file more bugs with Apple through http://bugreporter.apple.com so they know how big an issue it is.

yayaba
Apr 23, 2008, 09:32 PM
Ok gents, Beta 4 is out.

I actually didn't touch Beta 3 at all. I've been too busy the past few weeks to go back to my iPhone programming but it sounds like the problem is still there.

Anyone try Beta 4 yet? Have you seen the -10810 errors?

jtbandes
Apr 24, 2008, 07:30 PM
With Beta 4, the problem with my application (introduced in Beta 2) that caused it to crash and thus caused the -10810 issue has been removed, because the API was changed. So I don't know if the issue still exists, but I haven't personally had it happen. However, I haven't worked with it much yet.

jtbandes
Apr 26, 2008, 01:50 PM
I've been informed that people are still getting the crashes and -10810 errors with Beta 4. Rrgh.

GregX
Apr 27, 2008, 01:30 AM
Yep I crashed twice yesterday. Stability has improved and finally the flip device works again, stopped working in Beta 2 but now seems to be working.

Anyone else notice that user settings don't work on the emulator ? I "Understand" that it works on the real device but of course being non U.S getting into the "Developer programme" is near impossible. I am more than willing to pay my $99 to get hold of something that will allow real testing but Apple wish to restrict access to as many people as possible, so much for an open and free sdk !

Can't be long before Apple get taken down the Microsoft route ! Bet the anti competition lawyers are just itching to take them down !

Anyway, love the products and software that Apple produce but I hate all this cloak and dagger restriction *****... it's no wonder there is a whole industry of hackers out there, and thank god for peer to peer networks and the availability of software that vendors refuse to make available to those of us who want it and are willing to pay.

Just can't wait to Beta 4 firmware appears on the P2P networks so that I can test on my device again. Yes I got so arsed that I dabbled in the black arts and "borrowed" the beta 3 firmware for development purposes...

Good luck to anyone outside the US, maybe there should be a prize for the first non US citizen to get an "official" certificate from Apple to develop software for a fantastic device. Shame that the public is denied the choice of what they can install on something they actually have paid money to "own"

rant rant rant...