4 ms·

> instead rejected them first for a crash (sigh!) As a user, I'm glad Apple did that. As a developer, the one thing that I do dislike about Apple, is the dism

> instead rejected them first for a crash (sigh!) As a user, I'm glad Apple did that. As a developer, the one thing that I do dislike about Apple, is the dismal state of their documentation on how to actually take advantage of all their platforms' features. I have to begrudgingly admit that their nemesis Microsoft has always been way ahead in that department.

Illniyar 7y ago
I think their point was that the crash was because of the fact that: 1. Catalina had a lot of breaking changes, bugs and crashes that caused the apps to crash - which required special attention just for Catalina 2. They were given only 4 days to fix the mess that Catalina resulted in. At least in this case.
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 ago
  Catalina 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 ago
    Maybe, 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 ago
      Yes it would be the responsible thing to do as a developer to test your stuff on the OS before it comes out.
  - ravedave5 7y ago
    I'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.
jasonlotito 7y ago
Okay, but you left out the rest of that sentence. > and later for requiring UI changes, including showing a Save As panel for each generated file. So, Apple found a crash, and instead of completing the review (this assumes they could have, and benefit of the doubt here, they could have), they didn't. They found and issue, flagged it, and sent it back. This means the developer had to do work, resubmit, and then have another issue found. Rather than work through everything, the reviewer found one thing, dinged the app, and moved on. As a user, that means Apple is delaying apps longer than need be. Sure, fixing the crash is good, but I can't imagine they couldn't have reviewed the other parts of the app and said, "Fix the crash and this other two areas and you are good to go." That would mean a shorter turn around time, and as a user, I get a better product sooner.
- Razengan 7y ago
  > So, Apple found a crash, and instead of completing the review (this assumes they could have, and benefit of the doubt here, they could have), they didn't. Yeah, the crash could have prevented them from completing the review. > As a user, that means Apple is delaying apps longer than need be. Meanwhile, according to another outrage, Apple is •not delaying releases enough* and rushing out buggy apps and operating systems.
  - bitwize 7y ago
    Apple is delaying other people's apps and rushing out their own. Either way it saves them work.
cannonedhamster 7y ago
Apple's documentation is some of the worst most incomplete garbage I've ever had the displeasure of trying to read. When you literally need to go to third party people who just figured it out through sheer luck because features are fully undocumented and don't give tool tips, you've broken the user experience.
- deleted 7y ago
  [deleted]

Illniyar 7y ago

I think their point was that the crash was because of the fact that: 1. Catalina had a lot of breaking changes, bugs and crashes that caused the apps to crash - which required special attention just for Catalina 2. They were given only 4 days to fix the mess that Catalina resulted in. At least in this case.

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 ago
Catalina 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 ago
  Maybe, 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 ago
    Yes it would be the responsible thing to do as a developer to test your stuff on the OS before it comes out.
- ravedave5 7y ago
  I'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.

jasonlotito 7y ago

Okay, but you left out the rest of that sentence. > and later for requiring UI changes, including showing a Save As panel for each generated file. So, Apple found a crash, and instead of completing the review (this assumes they could have, and benefit of the doubt here, they could have), they didn't. They found and issue, flagged it, and sent it back. This means the developer had to do work, resubmit, and then have another issue found. Rather than work through everything, the reviewer found one thing, dinged the app, and moved on. As a user, that means Apple is delaying apps longer than need be. Sure, fixing the crash is good, but I can't imagine they couldn't have reviewed the other parts of the app and said, "Fix the crash and this other two areas and you are good to go." That would mean a shorter turn around time, and as a user, I get a better product sooner.

Razengan 7y ago
> So, Apple found a crash, and instead of completing the review (this assumes they could have, and benefit of the doubt here, they could have), they didn't. Yeah, the crash could have prevented them from completing the review. > As a user, that means Apple is delaying apps longer than need be. Meanwhile, according to another outrage, Apple is •not delaying releases enough* and rushing out buggy apps and operating systems.
- bitwize 7y ago
  Apple is delaying other people's apps and rushing out their own. Either way it saves them work.

cannonedhamster 7y ago

Apple's documentation is some of the worst most incomplete garbage I've ever had the displeasure of trying to read. When you literally need to go to third party people who just figured it out through sheer luck because features are fully undocumented and don't give tool tips, you've broken the user experience.

deleted 7y ago
[deleted]