iPhone Build crash

Unity Engine
,
1

Uncaught Exception:
*** -[PBXDebugScriptCommand debugSessionDidStart:]: unrecognized selector sent to instance 0x308d570

hmmmmm-

I get this if I want to change my Certificate in XCode- then I should be able to hit Build and Go, but it crashes. Any ideas? Has anyone tried changing certificates in Project settings in XCode?

2

Hello Chuck

I get the same error when trying to build again from Xcode…

Uncaught Exception:
*** -[PBXDebugScriptCommand debugSessionDidStart:]: unrecognized selector sent to instance 0x34fc550

Stack Backtrace:
The stack backtrace has been logged to the console.

Were you able to manage this?

3

Hi Andres

Actually once I get the build, I have been relaunching XCode and then selecting the code signing certificate to build with, Doing a Build->Clean All then a Build, then manually dropping the application on the iPhone with iTunes. This is only because I have multiple certificates.

I do have a machine where I use only 1 certificate, and a simple build-install from Unity works fine.

C-

4

Did anyone ever find a solution to this? I’m also getting the same error. If I press Continue I am able to load and play the game on the device. I have 2 profiles, one for an iPhone and one for an iPod Touch.

-James

5

Hello James

Unfortunately I don’t recall how that particular error was solved.

I was new to XCode (still I have no idea how to code in objective-c), that I had so many errors, sorry.

But it is a matter of getting familiar with Xcode and the whole building process. This may not be your case, but usually, when you trace an error, it will link to the problematic piece of code.

Andres

6

I’m having this problem and it sucks. I’ve spent 40+ hours this past week trying to build the simplest game, and now I get this. I’ve restarted EVERYTHING, cleaned the project, and so on. I don’t know what to do at this point other than take my anger out on small animals.

I have two dev profiles for iphone 2.1, but I mainly only use one. I’ve done about 20 compiles today, and about 20 minutes ago I started getting this. I’m feeling helpless at this point.

7

This is how I build everything now:

Test using Unity remote as much as possible, only deploy on the device as a final test.

In Unity: Build Settings->Build (NOT Build and Run)

Then open the file you built in XCode
In XCode: Project->Edit Project Settings (select certificate)
In XCode: Set to Device and Release
In XCode: Build (NOT Build and Go)
In XCode: Open the Products folder, right click on the filename.app, Reveal in Finder.
Drag that file onto iTunes then do a sync on the device.

This always works. Good luck!

8

ChuckT, thanks for taking the time to respond. Unfortunately, my iPhone syncs with another box, so the prospect of switching computers for every compile seemed a bit arduous. Here’s what I did instead:

  • Created a new APP ID Provisioning Profile (didn’t fix it, but I was going to have to do this anyway.)
  • Updated my iPhone firmware from 2.1 to 2.2.1
  • Uninstalled my 2.1 SDK + Xcode
  • Installed the 2.2 SDK + Xcode

I’m up and running now, but I’m kind of bummed that I lost half a day to a silly software glitch.