Can't compile in Xcode 7 - uint32-t error

Scripting Forums AppleScriptObjC and Xcode
#1

Hi All,

Has anyone encountered this error when attempting to build an ASOC project? It worked before but I need to update a small ASOC app for OS 10.11 and now get error:

"Reached end of file while looking for: uint32-t"

Any thoughts? This has one applescript file, no OBJc classes and is upgraded to ARC. maybe the change from GC to Arc caused this?

Thanks, Rob

#2

It sounds like a build setting problem. What version of Xcode are you using?

#3

Whoops – the subject tells me. Have you looked in the Report Navigator for more details?

#4

Geez, I was going along trying to sort out that error and now the build crashes!

NSInvalidArgumentException
[NSControllerObjectProxy copyWithZone:] unrecognized selectors sent to object…

10/30/15 10:30:18.415 PM iAlterImageO[23238]: (
	0   CoreFoundation                      0x00007fff8e85af0c __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x00007fff87ffb8e8 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff8e85dfcd -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
	3   CoreFoundation                      0x00007fff8e7988a1 ___forwarding___ + 1009
	4   CoreFoundation                      0x00007fff8e798428 _CF_forwarding_prep_0 + 120
	5   AppKit                              0x00007fff858f1441 -[NSCell _setContents:] + 74
	6   AppKit                              0x00007fff858f1315 -[NSCell setObjectValue:] + 486
	7   AppKit                              0x00007fff858f0f14 -[NSTextFieldCell setObjectValue:] + 88
	8   AppKit                              0x00007fff85acfca6 -[NSControl setObjectValue:] + 135
	9   AppKit                              0x00007fff85aaedbd -[_NSPlaceholderTextFieldPlugin showValue:inObject:] + 110

I upgraded to ARC, got rid of GC, checked the deployment targets etc. and there is no code (of mine) that runs at launch - the main window should open. I wonder if it is something in the nib that needs changing/upgrading…

! Rob

#5

That does suggest it might be a nib problem…

#6

And for anyone following along, it does seem to have been a nib problem. Weird…