I got hit with that annoying error too. Didn't encounter it on the mobile version...though it's kind of hard to tell when the mobile version is so prone to crashing anyway...