dev environment
Get flash to fully experience Pearltrees
debugserver is a console app that as server for remote gdb debugging. It is installed when a device is marked for development. It can be found in /Developer/usr/bin/debugserver . This is also the process invoked by Xcode to debug applications on the device.
debugserver - iPhone Development Wiki
tl;dr : Skip to the good part! A while back, Subversion 1.7 was released. It was a major upgrade, and included an entirely new way of internally keeping track of local working copies. Unfortunately, the svn tools in XCode 4 are not compatible with the new format, and thus could not read the status of (or commit) code on the server. Luckily, someone figured out a way to ‘patch’ Apple’s default SVN files with the new version. I first saw this on StackOverflow , and used it successfully for a few months waiting patiently for XCode to be updated.
Use SVN 1.7 in XCode 4.3+ | Tommy's Domain
The Most Useful Objective-C Code I’ve Ever Written « Vincent Gable’s Blog
Actually, it’s the most useful code I’ve extended ; credit for the core idea goes to Dave Dribin with his Handy NSString Conversion Macro . LOG_EXPR (x) is a macro that prints out x , no matter what type x is , without having to worry about format-strings (and related crashes from eg. printing a C-string the same way as an NSString ). It works on Mac OS X and iOS. Here are some examples, LOG_EXPR(self.window.screen); self.window.screen = <UIScreen: 0x6d20780; bounds = {{0, 0}, {320, 480}}; mode = <UIScreenMode: 0x6d20c50; size = 320.000000 x 480.000000>>Old versions of iPhone SDK
You need Apple developer account to login But Apple has disabled some of the links recently iPhone SDK 2.2.1 Leopard (10.5.4) http://developer.apple.com/iphone/download.action?path=/iphone/iphone_sdk_for_iphone_os_2.2.1__9m2621a__final/iphone_sdk_for_iphone_os_2.2.19m2621afinal.dmg iPhone SDK 3.0 (Xcode 3.1.3) Leopard (10.5.7) http://developer.apple.com/iphone/download.action?path=/iphone/iphone_sdk_3.0__final/iphone_sdk_3.0__leopard__9m2736__final.dmg
Update : symbolication is fixed in Xcode 4.1. Check this post for troubleshooting tips if you’re still having problems. Since XCode 4 was released, several iOS developers have reported that their crash reports are no longer symbolicated correctly, meaning that they can’t trace crashes to the code that caused them.
Can’t symbolicate XCode4 archive builds? | Two Bit Labs
One of the most requested features from developers, automated crash reports, can now be submitted by users via iTunes 8.2. Developers can access the reports via iTunes Connect. Crash reports are a vital tool developers use to help squash bugs and improve their software. The iPhone OS stores crash reports on the iPhone or iPod touch whenever an app crashes, and those get backed up whenever the device is synced with iTunes. Previously, however, developers had to rely on users to dig into these backups to get the report, and then send it in to developers manually.
iTunes now funnels iPhone crash reports to developers
Le 16-Mar-09, à 2:32 pm, Robert MacGregor a écrit: > Cool! > > Avez-vous un exemple de code montrant l'utilisation de l'exploitation forestière et la requête? En général, vous pouvez effectuer les opérations suivantes: / / Configurer l'enregistreur ASLogger * logger = [ASLogger defaultLogger]; [Enregistreur setName: @ "MyApp" installation: @ "" com.mycompany.myapp options: ASL_OPT_NO_REMOTE]; [SetFilter enregistreur: ASL_FILTER_MASK_UPTO (ASL_LEVEL_INFO)];
System logging via Cocoa - Toronto Area Cocoa and WebObjects Developers Group
Support - Discussions - Beginning Xcode (ObjC) Unit Testing - ...
Howdy. I'm following the Apple Xcode Unit Testing Guide, but I keep running into a problem when I try to build the Unit Test target. In my unit test class I #include and then attempt to use a class I have called "Item". Unfortunately, the Unit Test target build fails with a linker error: Ld build/Debug/UnitTestTarget.octest/Contents/MacOS/UnitTestTarget normal x86_64 cd /Users/michael/work/ObjC/FrontierMan setenv MACOSX_DEPLOYMENT_TARGET 10.6 /Developer/usr/bin/gcc-4.2 -arch x86_64 -bundle -isysroot /Developer/SDKs/MacOSX10.6.sdk -L/Users/michael/work/ObjC/FrontierMan/build/Debug -F/Users/michael/work/ObjC/FrontierMan/build/Debug -F/Developer/Library/Frameworks -filelist /Users/michael/work/ObjC/FrontierMan/build/FrontierMan.build/Debug/UnitTests.build/Objects-normal/x86_64/UnitTestTarget.LinkFileList -mmacosx-version-min=10.6 -framework Cocoa -framework SenTestingKit -o /Users/michael/work/ObjC/FrontierMan/build/Debug/UnitTestTarget.octest/Contents/MacOS/UnitTestTargetIf you’ve ever had to test an unreleased iPhone application or wanted to test yours with real world users, you’ll know what a pain it is. The UDID thing is bad enough, but the process of having to drag and drop .ipa and provisioning files to the copy of iTunes on the computer you sync with is ridiculous. Why on Earth can’t you do this over the air? That’s exactly what TestFlight brings to the table. The service provides an over-the-air app installation solution that is massively easier to use than the current iTunes sync model.
TestFlight: Super Simple, Over-The-Air App Beta Testing Comes To The iPhone
If you’re an iPhone or iPad app enthusiast, you’re probably familiar with the tedious procedure Apple mandates for developers testing new versions of their apps. But there is an alternative: TestFlight is a new service, just out of private beta, that brings the joy back to iOS beta testing. Helping a developer beta test a new version of an iOS app before it is submitted for approval usually goes something like this: First, you track down your device’s UDID (its unique identity code) and send it to the developer, who manually adds it to their pool of testers in the Apple Developer Center.