-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BridgeSupport problem? #4
Comments
What happens if you |
Seemed to work once perhaps, but problem recurred. It ends up with a blank I resorted to downloading the file from https://raw.github.com/dastels/MTGRules-rb/master/vendor/sqlite3/sqlite3.bridgesupport |
Wondering if motion.h isn't liking something...any ideas @kastiglione? |
OS X or iOS? |
iOS |
Can you try pointing your Gemfile to use motion.h from master (https://github.com/kastiglione/motion.h.git). If master fixes your problem than the solution is just for me to cut a new release. |
I can't reproduce the problem now! Feel free to close this, if it does come up again I'll attempt that fix. |
Chime in if the fix does or does not help. |
It happened again, and the fix did appear to do the trick. |
Once a new version of motion.h is released, I'll update the gemspec to use it. |
I release a |
Thanks Dave! 👍 Just pushed 0.5.2. |
Using both 0.0.4 of motion.h and 0.5.2 the error still persists. Manually copying sqlite3.bridgesupport from that MTGRules repo fixed the problem. |
@tylerjohnst Can you point your @Watson1978 recently submitted a pull request to motion.h that might address the problem you're seeing. I should release v0.0.5 anyway, but in the mean time if you do try master, please let me know. |
Same problem empty BridgeSupport file is built. |
I think I'm running into the same problem. I simply cloned the repo, ran 'bundle', then 'rake'.
I'm using rvm with ruby 2.2.0, and rubymotion version 3.8. |
I've seen people having success recently, but only with the master branch of |
I'm having this problem on High Sierra with motion 5.3 . Has anyone found a solution for this? I've tried the above fixes to no avail. |
Hi,
I've just started with RubyMotion and your sqlite3 driver was working great. But after upgrading RubyMotion to 2.22 (from 2.18),
The bizarre thing is that if I create a new RubyMotion project and copy the application code in, it works fine.
Any idea what's causing this error?
P.S. Thanks for writing this library!
The text was updated successfully, but these errors were encountered: