Looks like we can't reproduce the issue or there's a problem in the test case provided.
That was running beta3 but we've upgraded it to final as of today.
Please verify that you still having the issue.
Yes, the problem is consistent across the last several builds.
Fixing a different problem may have cleared it up.
I have two (of several) controllers called Login and and OrderNewTest
I noticed that every time I clicked on the OrderNewTest that the handler for the Login button fired as well.
Looking into the Controller action for Login, the controlQuery was set to 'button' rather than the ID of the specific button for the login controller.
It looks like it was catching all button Tap events. That would mean that it was logging in every time I tapped on the OK button for alerts.
This would have set a mask and should later have cleared it after login. I am not sure why it wasn't eventually clearing but making the event handler more specific seems to have cleared the problem.
Glad to hear you resolved it.
Not as glad as I am. There were several other odd behaviors that cleared up once I found this.