Dilemma after moving Project.
I had a nice working project saved at 3 am this morning. Got up at 8:30, and added 11 tick boxes with true/false properties, and added them to the .plist saving and reading handlers. Also added an internal ‘Scripts’ folder, and dragged in an .rtf example file, which opens with button.
Then, before testing, stupidly dragged the Project from the desktop to the folder I keep my Projects in.
Built it, tried to open, and got a ‘copyWithZone' error below.
Have researched, and it seems most likely I have to somehow ‘re-link’ my xib file to my Project. Can’t find exactly HOW though. Nothing on what to do with ASCObjC Project for MacOSX.
Path to Project is…
/Users/OzSanta/Documents/My XCode Projects/MM Sierra App Store/Mail Manager Accountancy/Mail Manager Accountancy/Base.lproj/MainMenu.xib
Any, any help please? Tried dragging back to Desktop, too late. Only simple things added!! I DID accidently drop the .rtf file outside the ‘Scripts’ folder, then dragged it in. That cause a problem?
If no advice, I’ll have to restore from Time Machine, and re-build step by step. BUT, would like to know WHY this happened!
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[AppDelegate copyWithZone:]: unrecognized selector sent to object <AppDelegate @0x61000022eaa0: OSAID(4) ComponentInstance(0xdf0000)>'
terminating with uncaught exception of type NSException
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff8d3442cb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffa215448d objc_exception_throw + 48
2 AppleScriptObjC 0x00007fff8bb4aa23 -[BAObjectProto methodSignatureForSelector:] + 0
3 CoreFoundation 0x00007fff8d2b6755 ___forwarding___ + 1061
4 CoreFoundation 0x00007fff8d2b62a8 _CF_forwarding_prep_0 + 120
5 AppKit 0x00007fff8add4b4a -[NSCell _setContents:] + 73
6 AppKit 0x00007fff8ade1199 -[NSCell setObjectValue:] + 166
7 AppKit 0x00007fff8ade10a6 -[NSTextFieldCell setObjectValue:] + 93
8 AppKit 0x00007fff8aeb70c2 -[_NSPlaceholderTextFieldPlugin showValue:inObject:] + 110
9 AppKit 0x00007fff8aeb69cc -[NSValueBinder _adjustObject:mode:observedController:observedKeyPath:context:editableState:adjustState:] + 391
10 AppKit 0x00007fff8aeb67b6 -[NSValueBinder _observeValueForKeyPath:ofObject:context:] + 286
11 AppKit 0x00007fff8aeb661f -[NSTextValueBinder _observeValueForKeyPath:ofObject:context:] + 43
12 AppKit 0x00007fff8ae0bc03 -[NSObject(NSKeyValueBindingCreation) bind:toObject:withKeyPath:options:] + 773
13 AppKit 0x00007fff8ad8181d -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 1284
14 AppKit 0x00007fff8ad78af0 loadNib + 375
15 AppKit 0x00007fff8ad7803a +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 308
16 AppKit 0x00007fff8ad77df2 -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201
17 AppKit 0x00007fff8ad77baf +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 414
18 AppKit 0x00007fff8ad72b2b NSApplicationMain + 498
19 Mail Manager Accountancy 0x00000001087b68a2 main + 98
20 libdyld.dylib 0x00007fffa2a3a235 start + 1
toggle quoted messageShow quoted text
Did you try looking at the 'file attribute' inspector in the Utilities pane of Xcode to check how Xcode is referencing your XIB? If you had an absolute path and moved your project Xcode wouldn't be able to find your XIB. But I this should cause a build error not a runtime error. Did you do a clean, then build?
On Aug 27, 2017, at 22:02, Brian Christmas <ozsanta@...> wrote:
By "project" do you mean just the .xcodeproj, or the enclosing folder with the project file and source files?
Moving just the .xcodeproj will definitely break everything, because by default it uses relative paths to find all the other files.
Moving the entire project folder should be OK; if it breaks your build it's probably because you've ended up with absolute paths to some files, which are now broken links. Use the File Inspector pane to look at the paths for the files in your project.