On Aug 27, 2015, at 07:53 , Alex Zavatone <[email protected]> wrote: > > How, in good conscience, is this NOT DONE?
I of course don’t have an official answer, but it seems to me that Xcode has to be able to re-submit an “older” app. If you’ve previously submitted a 32-bit app, it should be possible to update the app (for, say, security reasons) even though the app is obsolete and will never be *functionally* updated ever again. There have been scenarios in the past where it was allowable to upload an app that didn’t follow the current guidelines. For a long, long time after the MAS required sandboxing it was possible to submit unsandboxed apps to the MAS to fix bugs. It may still be possible, for all I know. > why should any app developer find out AT THE LAST MINUTE that their app > violates the rules for submission even AFTER it has passed regular validation? If you’re dealing with this “at the last minute”, in the sense that you will (say) lose money if the app isn’t released on schedule, it’s your fault if you don’t leave enough time for last minute glitches, not Apple’s. I realize it’s extremely frustrating when something goes wrong, but Apple is not your mother. I can hear you starting to say, “Yes, but …”, but there really aren’t any buts. You don’t run your own business that way either — you don’t expect to be sued by a customer for losses caused by a bug, a crash or the late release of your software, do you?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
