3 ms·
In context though it is still Apple's issue: > After releasing the Catalina Golden Master build to developers on October the 3rd, we immediately finished fixin
by Someone1234 7y ago
In context though it is still Apple's issue:
> After releasing the Catalina Golden Master build to developers on October the 3rd, we immediately finished fixing any new crash and issue we could find over the weekend. In our opinion, leaving developer just four (4!) days over a weekend with a public release on October the 7th is not very professional. While we still updated our applications in time, Apple did not review them for the AppStore, and instead rejected them first for a crash (sigh!), [...]
- jldugger 7y agoCatalina had been available to the public for testing since like WWDC; unless these were late breaks only found in GM, it's a tough pill to swallow that these urgent bugs couldn't have been addressed before GM shipped.
- semiotagonal 7y agoMaybe, but prior to the "Golden Master" release are you really testing your stuff, or Apple's? Leaving such a small window between Apple getting its act together with the GM, and a hard deadline for third parties to get their act together, is rough.
- rstupek 7y agoYes it would be the responsible thing to do as a developer to test your stuff on the OS before it comes out.
- ravedave5 7y agoI'm not with theis company - my company also had major issues with Catalina. There were major bugs released in each beta. Several were fixed without any release notes mentioning so. We wasted several days of an engineers time tracking down an issue that was fixed in a new beta with no mention. Incredibly frustrating.
- Someone1234 7y ago> unless these were late breaks only found in GM That's exactly what the article and the quote above says there was: > we immediately finished fixing any new crash or issue we could find over the weekend NEW crashes or issues. In the GM. In four days.