Closed JakeTheSnake3p0 closed 7 years ago
Sorry about the long wait. I think this is unrelated to the Rails version but probably had to do with your environment. E.g., I've gotten reports that under Rubymine this issue may occur. I just pushed a new release 0.3.0.rc1 which is compatible with Rails 4.2 and later and also fixes the Rubymine problem. Let me know if you still have problems with this.
I just started receiving this error recently - most likely after my recent rails version update.