Closed markrickert closed 10 years ago
Mark, I spun up a blank PM project and added the gem and am not getting an error.
Cyclical error report here: http://hipbyte.myjetbrains.com/youtrack/issue/RM-361
If you clone my demo app, does it cause a problem on your machine Mark?
I'm trying to debug and narrow it down to what is causing the issue... if i copy my gemfile and rakefile over, it happens.
I'm glad i got this new MBPro... running bundle install && rake clean:all && rake pod:install && rake
takes a toll on the processor!
OK... I've got it. add:
gem 'formotion'
to the Gemfile
. BOOM. Reproducible.
WTF? Why would formotion
cause this error in a DIFFERENT vendored objective-c library?
Any ideas, @clayallsopp ?
Most definitely appears to be a RubyMotion bug
What @clayallsopp said (which is why we already have the ticket tracking it). One thing you can do, as a workaround, is to manually fix the BridgeSupport metadata that’s generated for PKRevealController.
Hey @markrickert - was there a new release of RM that fixes this issue? If so just wanted to make a note of what version of RM you should be using (or higher) and close this. Thanks!
Not yet. I switched to a fork (and branched it) that uses ECSlidingViewController
but it's iOS 7 only, so not sure if you want to switch the main repository or not.
I forked from this one: https://github.com/josch1710/promotion_slide_menu/tree/ECSlidingViewController and here's the fork I'm successfully using in my app: https://github.com/markrickert/promotion_slide_menu/tree/ECSlidingViewController
Temporary fix, edit the PKRevealController.h
Find the three lines that look like this:
typedef enum : NSUInteger
And make them look like this:
typedef enum // : NSUInteger
Commenting out the forced typedef name, makes it compile correctly.
I'm starting with a fairly clean app.
Put the gem into my
Gemfile
, ranrake pod:install
and thenrake
and I get this:I also tried manually including the
PKRevealController
in myRakefile
and doing arake clean:all
but to no avail.Thoughts?