Crash when building for iOS 7 with Xcode 6.01 (iOS8 SDK)

[jayroh]

I've managed to replicate this on two different machines and am at a loss as to why this is occurring. This might be a Core Data specific problem because things work fine when building for iOS7 w/Xcode 5 ... and when building for iOS8 w/Xcode 6. I thought I would post this here in the off chance this is something someone else has seen, OR someone sees in the near future.

Details for the crash are as follows:

1. Install Xcode 6.01
2. Install the iOS 7 emulator in Xcode 6.01. (Xcode -> Preferences -> Downloads)
3. Pull down this code: git clone [email protected]:jayroh/sample-cdq.git && cd sample-cdq && bundle
4. Run the app using a 7.x emulator: rake target=7.1
5. The app will start up in the iPhone 5S / iOS 7.1 emulator and give you the repl.
6. To trigger the crash, run the following in the repl:

p = Post.new and p.active = 1

More can be found at this sample app, including the crash-log

[kemiller]

Hey Joel! I'll have a look. Does it crash if you set p.active to a real boolean?

[jayroh]

Yeah, Ken. It'll crash on that too -> p = Post.new and p.active = true

So odd that the code run in the repl and the contents of one method in the model feel disparate but cause this. Really weird.

Thanks for the quick response too ;). Appreciate it

[kemiller]

Smells like an RM bug. 2.34 is coming shortly with Xcode6 issues.

[jayroh]

Well, just installed RM 2.34 and the crash is still occurring. Is this a case where it'd be more helpful to post on the RM mailing list and/or post to the RM bug tracker?

I ask because, for me, this is a case of "I don't know what I don't know" regarding what could be causing this.

Thanks for your time, Ken.

[kemiller]

So I don't know what's going on, but I don't think CDQ is responsible. It fails when using setActive(1) which I frankly don't monkey with at all. It does seem to work with setValue(1, forKey: 'active')

I'd file a ticket with HipByte and see what they think...

[squidpunch]

Not sure what is going on either but I tested a little and I can see that it definitely crashes when targeting 7.1 from Xcode 6 or Xcode 6.1. Using Xcode 5.1 targeting 7.1 runs without crashing.

This is still the case using RubyMotion build (2.25)

🐼

[jayroh]

Yeah it's weird ... but ... we settled on sticking to xcode 5.1 for the time being and building for 7+.

I would hope over the next few months this will get ironed out somewhere between RM or Xcode and that'll be that. Just hope that's before we need to use any of the new stuff in iOS 8 . /shrug