background preloader

Dev environment

Facebook Twitter

Ios - Xcode 6 - Launch simulator from command line. 7 alternatives to TestFlight | VentureBeat | Dev | by J. O'Dell. Over the years, TestFlight became a tool mobile app developers relied on. But parent company Burstly’s recent acquisition (by Apple) and termination of Android support has developers looking for alternatives. Getting your beta to testers with ease is important. But some platforms, particularly iOS, make the process a hassle. There are many predictions about Apple’s future plans for TestFlight. But for now we’ll focus on TestFlight alternatives for iOS, Android, and Windows developers. HockeyApp | [paid] HockeyApp not only helps you distribute betas, but is a complete beta testing suite. With HockeyApp, you don’t need extra tools.

What’s better is that HockeyApp is available for the iOS, Android, and Windows platforms. HockeyKit | [free] One thing developers loved about TestFlight was its price. HockeyKit is the self-hosted, open source version of HockeyApp. Don’t know anything about servers? As you’d expect, HockeyKit has fewer features and is only available for iOS and Android apps. Iphone - sent to deallocated instance. Debugserver - iPhone Development Wiki. Debugserver is a console app that as server for remote gdb or lldb 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. If you're using iOS 7, see Debugging on iOS 7 for more context. Command line options debugserver can be invoked with debugserver [<options>] host:<port> [<prog-name><arg1><arg2> ...] Where options can be: Patching for process attaching The vanilla debugserver lacks the task_for_pid() entitlement. 0. cd ~ 1.

Lipo -thin armv6 /Developer/usr/bin/debugserver -output ~/debugserver 2. <! 3. Ldid -Sent.xml debugserver Alternative Instructions (64-bit compatible) Alternatively if you are on a Mac with Xcode, installed you can follow Peter Steinberger's instructions to add entitlements to the debugserver that comes with Xcode.

I am not sure if you need an Apple developer membership and certificate to add the entitlements. 1. 2. <? 3. 1. . Example: Redirecting debug output from XCode 4 console to a log file. Use SVN 1.7 in XCode 4.3+ | Tommy's Domain. 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. Soon enough, there was a new version of XCode! And it was available through the Mac AppStore! After installing 10.7.3 and downloading XCode 4.3.1 from the Mac AppStore, I started it and immediately went to the repositories section, expecting to see my working copies listed and ready to be updated and committed.

The good news is, upgrading SVN inside the package isn’t too different from upgrading the old way. That’s it! Iphone - Xcode 4.2 showing the wrong line of code on error. Objective c - App crashes when launching after updating app via HockeyApp. Iphone - Xcode 4: create IPA file instead of .xcarchive. Symbolicating iPhone App Crash Reports. 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>> LOG_EXPR(self.tabBarController.viewControllers); self.tabBarController.viewControllers = ( “<UINavigationController: 0xcd02e00>”, “<SavingsViewController: 0xcd05c40>”, “<SettingsViewController: 0xcd05e90>” ) Pretty straightforward, really.

LOG_EXPR(self.window.windowLevel); self.window.windowLevel = 0.000000 LOG_EXPR(self.window.frame.size); self.window.frame.size = {320, 480} Give it a try. How It Works The Macro, Line By Line Limitations Arrays __func__ 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) here iPhone SDK 3.0 (Xcode 3.1.3) Leopard (10.5.7) iPhone SDK 3.0 (Xcode 3.2) Snow Leopard (10.6.0) iPhone SDK 3.1 with Xcode 3.1.4 Leopard (10.5.7) iPhone SDK 3.1 with XCode 3.2.1 for Snow Leopard (10.6.0) iPhone SDK 3.1.2 with XCode 3.1.4 for Leopard (10.5.7)

Can’t symbolicate XCode4 archive builds? | Two Bit Labs. 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. I’ve traced this problem down to the Perl script that XCode uses to map the addresses in a crash report to their symbols, symbolicatecrash. I’ve patched the script to get it working, which you can download here. Archiving in XCode 4 It’s been possible to archive a build in XCode for a while, primarily to preserve it in a place you could get to from the Organizer. The Problem In XCode 3.x, Build and Archive created an .ipa file.

The Fix First symbolicatecrash does a Spotlight search for the .dSYM directory for the UUID of the app from the crash log: mdfind "com_apple_xcode_dsym_uuids == 2E0EB467-3372-3235-A692-40754870C921" What’s Next? iTunes now funnels iPhone crash reports to developers. 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. Now, whenever a device is synced and iTunes recognizes there are new crash reports, a program called MDCrashReportTool, which appears to be part of the upcoming iTunes 8.2 update, sends these reports to Apple.

Apple then funnels the reports to the correct app developer's iTunes Connect account. This is a sample of the statistics Apple provides developers via iTunes Connect. Credit: Bryan Henry. Objective-C equivalent of Java packages. 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_64cd /Users/michael/work/ObjC/FrontierMansetenv 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/ -mmacosx-version-min=10.6 -framework Cocoa -framework SenTestingKit -o /Users/michael/work/ObjC/FrontierMan/build/Debug/UnitTestTarget.octest/Contents/MacOS/UnitTestTarget Suggestions?

Thanks! TestFlight | iOS beta testing on the fly. TestFlight: Super Simple, Over-The-Air App Beta Testing Comes To The iPhone. If 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.

How do I know? I’ve actually used it. Obviously, TestFlight hopes all customers have the same reaction I did. Beyond simple over-the-air installation, another big plus to TestFlight is that you can group testers together to serve them up different versions of your app. All of this is still subject to Apple’s device testing limits (which is why the UDID is still needed), but again, TestFlight makes the process so much better. No Crash logs showing up / TestFlight Problems / Discussion Area - TestFlight Support. TestFlight makes iOS app testing a lot easier | Utilities | iOS Central. 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. The developer then e-mails you a testing copy of the app along with a provisioning file (a sort of temporary license for the app), both of which you have to drag into iTunes before syncing your device. Rinse and repeat for every developer you help test apps for, and every app you help test. Thanks to iOS 4, TestFlight can alleviate most of the pain of iOS beta testing.