> In general, a crash on the latest OS update is a good reason for rejection because you're going to have to fix it sooner or later anyway. Better to fix it now rather than have to come back to it later.
That's true, but how do you fix a bug you can't reproduce with an unreleased patch you can't acquire, which is probably the same for the general public?
Of course, but this situation should not happen. Reviewers should be using the latest OS update that is available to developers. That has always been my experience, but my experience is mostly on iOS not macOS.
In particular because Apple's stated position is "Developers should always be developing against the latest released version of the platform" (being iOS or macOS).
Throwing a rejection because of a bug that can only be reproduced on an unobtainable minor patch release doesn't seem to fit with that guideline.
That's true, but how do you fix a bug you can't reproduce with an unreleased patch you can't acquire, which is probably the same for the general public?
There has to be some flexibility here.