Hi all. Been out for over a week. Weather warming and business picking up. Slowly losing my extra development time, but still so much left to do..... Wondering if I should update to the new XCode, or just keep as is. Any issues? Looked at the change log, good stuff. Especially fond of the image gallery improvements. I bet that was a big project! Also looking forward to the upcoming quiz release. Thanks.

Welcome back R2, figured you were boating a bit and makin' a few bucks? Xcode 4, heard a few things. I have it running here on another machine. It's a bit to get used to with the layout changes and sorts but it's basically the same thing. I never switch 'fast' to the latest release, usually give it a few weeks to officially jump-over. We've heards a few beefs about configuring some build settings and few other issues. It seems to work without too much trouble so far but not very many people have switched (I think). It's looking like Xcode 3.x will be around for awhile based on the internet-uproar about Apple charging $5.00 to get the newset. Funny. A link clearly reads 'You can use Xcode 3.x for FREE by clicking here' and everyone is still worked up over the silly $5.00 fee. Whatever. Glad to see the avatar again.

I have switched to Xcode4 and so far...no issues. I like the new interface and central window idea much better. I have also submitted my first app to apple for review (pending) using XCODE 4 and IOS4.3 SDK. Waiting to hear back from apple.

Well, here is something I came across today. I was testing/building fine on XCODE 4 with IOS4.3 on the iphone simulator without any issues, I was also able to install to a 4G ipod touch running 4.3 without problems. All this using a buzztouch 1.5 application. Now, when I tried to run it on the iPad simulator things did not go well. build succeeded but when it tries to attach to the device the code crashed. (simulator and/or iPad...same thing) //connection failure -(void)connection:(NSURLConnection *)connection didFailWithError:(NSError *)error { [BT_debugger showIt:self:[NSString stringWithFormat:@connection: didFailWithError. Code: %@, %@, [error code], [error localizedDescription]]]; [self downloadFileCompleted:[NSString stringWithFormat:@ERROR: Code: %@ Description: %@, [error code], [error localizedDescription]]]; } NOTE: Thread1:Program received signal: EXC_BAD_ACCESS. In addition, for some reason it also reports these errors: a) Lexical or Preprocessor Issue. Extra tokens at end of #import BT_fileManager.h; (should this semi colon be here ???) b) Semantic Issue: //start request NSMutableURLRequest *theRequest = [NSMutableURLRequest requestWithURL:escapedURL cachePolicy:NSURLRequestUseProtocolCachePolicy timeoutInterval:25.0]; [theRequest setHTTPMethod:@GET]; if(self.remoteConn = [[NSURLConnection alloc] initWithRequest:theRequest delegate:self]){ receivedData = [[NSMutableData data] retain]; }else{ [self downloadFileCompleted:@Error - could not initialize connection.]; } c) Semantic Issue //start request [theRequest setHTTPMethod:@POST]; [theRequest setValue:postLength forHTTPHeaderField:@Content-Length]; [theRequest setValue:@application/x-www-form-urlencoded forHTTPHeaderField:@Content-Type]; [theRequest setHTTPBody:postData]; if(self.remoteConn = [[NSURLConnection alloc] initWithRequest:theRequest delegate:self]){ receivedData = [[NSMutableData data] retain]; }else{ [self downloadFileCompleted:@URL Error]; }

No, the semi-colon should NOT be there. remove it from BT_downloader.m. This one tiny issue could be the reason for the other issues. Kindly remove that semi-colon. It's in BT_downloader.m near top of the file. See what happens if you re-build. We'ev removed this crazy semi-colon from the download server but you don't have to re-donwload the entire project, just remove the stray semi-colon and see what happens. Strange that it would cause issues on some devices and not others - sigh...

Thanks David. I removed the semi-colon from BT_downloader.m as you said and tried another build. No issues, but won't run on iPad 4.3 simulator yet. //connection failure -(void)connection:(NSURLConnection *)connection didFailWithError:(NSError *)error { [BT_debugger showIt:self:[NSString stringWithFormat:@connection: didFailWithError. Code: %@, %@, [error code], [error localizedDescription]]]; [self downloadFileCompleted:[NSString stringWithFormat:@ERROR: Code: %@ Description: %@, [error code], [error localizedDescription]]]; } It now says: Thread1: Program received signal: EXC_BAD_ACCESS I will try to re-dowdload the source code....

After re-downloading and rebuilding it now works perfectly in 4.3 iPhone and iPad simulator. Cool! Thanks for the great help.

Unfortunately, when I tried it on my actual iPad, it started to run for a second, then crashed with msg: Program received signal: EXC_BAD_ACCESS The debugger has a message too: warning: UUID mismatch detected with the loaded library - on disk is: /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk/Developer/usr/lib/libXcodeDebuggerSupport.dylib //connection failure -(void)connection:(NSURLConnection *)connection didFailWithError:(NSError *)error { [BT_debugger showIt:self:[NSString stringWithFormat:@connection: didFailWithError. Code: %@, %@, [error code], [error localizedDescription]]]; [self downloadFileCompleted:[NSString stringWithFormat:@ERROR: Code: %@ Description: %@, [error code], [error localizedDescription]]]; }

Where is this connection failure showing up? In the console? UUID errors are tricky. Because you're installing onto the actual device with Xcode, it's critical that all sorts of things match up. See this: http://stackoverflow.com/questions/215252/uuid-mismatch-detected-with-the-loaded-library I can say that UUID erros are 100% related to the Xcode version AND the iPad version and their happy marriage. They have to be exactly the same or issues arise. These kinds of things happen almost everytime Apple releases new Xcode complier and iOS for devices. Tough for them to keep it all straight. See if that article / URL is understandable.