How is that nuts? It's pre-release software, which is subject to change. Why would you submit a patch to fix an issue which might change all over again before it's released?
Seriously, if this is your bar for being nuts, then I'm glad you don't have anything to do with the iOS ecosystem.
I don't think that's true anyway. I just saw an update from Dropbox yesterday that had the update text "Fixes most common crashes for users running the iOS 9 Beta".
Sometimes Apple tightens up their APIs, which may have been a gray area on previous versions of the OS. Being able to future-proof your app when the new OS ships is a good thing.
Apple is just nuts. This makes me glad I don't have anything to do with their ecosystem.
It's very hard to be the "Lord of the Castle" and not end up doing something that seems crazy and unjust to someone. This is especially true in the face of numerous attempts to exploit and mobs of the noisy clueless. Even if you go to the trouble of instituting some sort of sophisticated judicial process, someone is going to cry "foul!"
The above can also be taken as an argument for why one might want to avoid being part of the "ecosystem."
Seems reasonable to me. They are presumably blocking app updates that take explicit dependencies on new/changed APIs in the preview. If they allowed apps to take dependencies on these, they'd effectively be forced to support the API surface exposed in the preview indefinitely. (Alternatively, imagine the outrage when they broke a bunch of apps with the final release.) Disallowing this enables them to iterate on the preview more effectively, which is the entire point of the preview.
iOS 9 is pre-release software with an expectation of changing APIs before it releases. So makes sense for them to have a hold on iOS 9 focused updates till release.
Apple is just nuts. This makes me glad I don't have anything to do with their ecosystem.