Quote:
Originally Posted by CommanderData
Just to keep the wait thread on topic here- I actually received a rejection last night for a stupid bug I introduced with a new preference setting at the last minute. It went unnoticed by me because it only affected fresh, new installs. My final few tests before packing up the binary on 3/11 were just overwrites of my current app file 
They actually sent me crash logs and a description of how they reproduced it, but they weren't timely at all- the logs were over 24 hours old by the time they were e-mailed to me!
Anyway, stayed up really late last night and rolled my 1.3 and new 1.4 update work into one big update for Rogue Touch (including fixing that *%^$#& preference issue). So here I am again...
Does anyone know if they reject an update binary if you get any sort of preference when submitting the replacement? Or is it "back of the line, buddy!" for me  |
Back to the start of the line I'm afraid.
Made exactly the same error myself a while back.
Still, fair nuff. A bug's a bug.
