Case 25818
Hi Rob - any update on this case - Case 25818 ?
Not specific to that bug. I know that Widgets are being worked on the finishing touches on a huge storyboard update is getting pretty close, so perhaps between the two, it might be addressed.
hope so - having to disable “tap” events on the listview kind of gives a useability issue - users wanting to click in an item in the view click multiple times I note, not really knowing the difference between a fast tap and a slower press
Hi Rob - any update on this case - Case 25818 ?
Not specific to that bug. I know that Widgets are being worked on the finishing touches on a huge storyboard update is getting pretty close, so perhaps between the two, it might be addressed.
hope so - having to disable “tap” events on the listview kind of gives a useability issue - users wanting to click in an item in the view click multiple times I note, not really knowing the difference between a fast tap and a slower press
Hi Rob - any update on this case - Case 25818 ?
I’ve just got a rejection from Apple on an app update and I’m suspecting it may be due to this, and that the apple tester may have done a “tap” and not a “press”. Have just provided feedback through resolution center…hope they’ll accept the concept of avoiding taking action on a “tap” as it’s likely to be a user error…if not may have to come back to Corona with advice on how to work around this issue with the events passing through…
We found that your app exhibited one or more bugs, when reviewed on iPad running iOS 7.0.4 on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
Specifically, when users select the play button on your menu screen, and select the first level. There is no response from your app. Users are unable to proceed and play the game.
It’s still in the queue to be fixed.
Rob
ok - will wait and see what Apple say - actually as a work around perhaps I could throw up an invisible rect before calling the overlay, and then trying to get it to trap the “tap” event thanks seeping through at the point the overlay is closed…
Hi Rob - any update on this case - Case 25818 ?
I’ve just got a rejection from Apple on an app update and I’m suspecting it may be due to this, and that the apple tester may have done a “tap” and not a “press”. Have just provided feedback through resolution center…hope they’ll accept the concept of avoiding taking action on a “tap” as it’s likely to be a user error…if not may have to come back to Corona with advice on how to work around this issue with the events passing through…
We found that your app exhibited one or more bugs, when reviewed on iPad running iOS 7.0.4 on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
Specifically, when users select the play button on your menu screen, and select the first level. There is no response from your app. Users are unable to proceed and play the game.
It’s still in the queue to be fixed.
Rob
ok - will wait and see what Apple say - actually as a work around perhaps I could throw up an invisible rect before calling the overlay, and then trying to get it to trap the “tap” event thanks seeping through at the point the overlay is closed…