Earlier today, I upgraded from RubyMotion v 2.24 to v 2.26. Immediately after the upgrade, I attempted to run a RubyMotion app that I’m working on. The result?
What happened? It just ran a few minutes ago, right before the upgrade! Was RubyMotion broken? Was it time to reach out to the Twitterverse or Stack Overflow for assistance?
Every time RubyMotion build an app, it stores the results in the ./build directory. Since I had just done an upgrade, it was possible that remnants from a v 2.24 build were interfering with my new v 2.26 build. The solution?
And now the app runs fine. Crisis averted. Back to work!