Hacker News Reader

While RM-3 itself is only 4 months old, the bug's been around and discussed since RubyMotion first came out (e.g. http://blog.blazingcloud.net/2012/07/16/rubymotion-block-sco...).

They used a bug tracker that wasn't publicly viewable until they migrated everything to YouTrack earlier this year (I reported it last August).

View on HN

Laurent himself replied to that blog post saying the bug was resolved in RM v1.20. What's the difference between RM-3 and what that post describes? They read very similar to me.

Maybe a regression? It does sound like the exact same issue at a glance.

Reply on news.ycombinator.com