Reporting Bugs

Oh noes!  There’s a bug in Corona!  What to do?

Read this and all will be revealed!

The bugs that get fixed fastest are the ones with a straightforward reproducible case that an engineer can run and immediately see the problem (this might mean including an explanation of why what happens when the code is run isn’t what’s expected).  Bug reports that consist of “Its broken!!!1!” and 1000 lines of Lua spread across 19 files generally don’t get much attention as we’re really busy working on new features and the bugs we can easily understand.  Also remember that the environment is always important when it comes to buggy behavior so if the Android device you’re seeing a problem on happens to be a lawnmower, be sure to mention that!

This topic is closed to further posts but please feel free to start new topics on the subject of specific bugs or the generalities of bug reporting.