Skip to content

Example app raising an exception... #4

Closed
Bodacious opened this Issue Sep 12, 2012 · 1 comment

2 participants

@Bodacious

hey - I really like the look of MotionData - I'm having trouble getting it to work though. I get the same error when loading it into my app or running the example Recipes app:

uninitialized constant MotionData::MotionDataManagedObjectBase (NameError)
*** Terminating app due to uncaught exception 'NameError', reason: 'uninitialized constant MotionData::MotionDataManagedObjectBase (NameError)

Can you please explain how I can get the basics up and running in a standalone app? Thanks

@jonathanpenn jonathanpenn pushed a commit that referenced this issue Sep 13, 2012
Jonathan Penn Fixed issue #4 where MotionDataManagedObjectBase was missing from
Recipies
ef37097
@jonathanpenn
Collaborator

Take a look at this commit ef37097, and you'll see what to do.

Apparently, in all the shuffle going on, the Recipies example broke for two reasons.

  1. Two new ruby files were created (predicate.rb and scope.rb) when those parts were extracted out but they weren't added to the Rakefile manifest for the example.
  2. Eloy needed to drop down to Objective C to do some swizzling magic to get things to work and those files were referenced in the ext directory in the root of the project. I needed to add that reference to the Rakefile in the Recipies example, too.

The app builds fine for me now. I'm going to go ahead and mark this as closed. Feel free to reopen it with more info if it's still not working for you, or leave further comments if you want clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.