Add a "Must Fix for Next Release"

Originator:craig.hockenberry
Number:rdar://19921616 Date Originated:23-Feb-2015
Status:Open Resolved:
Product:iTunes Connect Product Version:N/A
Classification:Enhancement Reproducible:Not Applicable
 
Summary:
In the current version of xScope, there is a memory leak caused by a change in OS X 10.10.2. While the Loupe is in the background grabbing the screen, something in the frameworks is leaving images in the autorelease pool. The fix is literally two lines of code that forces the pool to empty.

But that's not why I'm writing now.

This fix was submitted two weeks ago on February 2nd. A week later it went into review and was quickly rejected. The problem was that a buy button was accessible from our Help window.

The bulk of the help is static and built into the app, but there is a part online that we can update easily. This makes it really easy easy for us to addtips and other useful information for our customers. But since it's just a web browser, it's possible to wander into a part of our site that shows a header with mentions the word "buy" which is not allowed per rule 7.15. (Yes, the buy button is for something the customer has already purchased and is actively in the process of using, but technically it's still a violation.)

My issue is the way that we must fix these problems. In this particular case, the issue was resolved by editing some HTML on our server, not by changing anything in the app itself. But we still must submit a "new" binary and go through the lengthy review process again. This is a huge waste of time for both developers and app reviewers (who are clearly lagging behind these days.)

I think there's an easy way to fix these minor transgressions that would benefit both parties: add a new kind of approval with strings attached. A "Must Fix for Next Release" state where the app can go into "Ready for Sale" but the issue remains in the Resolution Center. At that point, both the app reviewers and developer know that an issue has to be dealt with before it's approved the next time.

Steps to Reproduce:


Expected Results:


Actual Results:


Version:


Notes:


Configuration:
N/A

Attachments:

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!