91–100 of 441 posts
Well, why the hell is electron/chromium using private APIs? That seems like the real problem here...
Earlier quoted context omitted.
Those aren't native apps.
"Now it’s incredibly simple to start building a native Mac app from your current iPad app." — https://developer.apple.com/mac-catalyst/ Literally every paragraph of copy on this page emphasizes them as native apps.
Well, why the hell is electron/chromium using private APIs? That seems like the real problem here...
Its looks as if the Electron team had the assumption that developers would be unlikely to distribute their Electron Mac apps via the App Store, but instead as a DMG or zip which doesn't require Apple reviewing private APIs.
Earlier quoted context omitted.
Calling private API is not nonsensical Apple policy, and you're reducing the instances in which rejection is nonsensical Apple policy.
The post shot to #1 on HN in no time, because the developer community thinks this rejection, and it's backing policy to be nonsensical.
Which is not a homogenous group, both in ideals and for why they'd upvote a submission like this.
> this rejection, and it's backing policy to be nonsensical
They're different things. I personally think the rejection is perfectly sensical in the context of the backing policy, with which I don't fully agree.
Probably not a big deal for publishers - most (non-tech) people I know download Electron apps via their own website e.g. Slack, Notion, etc.
Earlier quoted context omitted.
> "Keep trying to submit, and we might just ban you forever" is insane. I was under the impression that if you're being annoying and keep trying to submit a build with private API, making App Store Review's life hard, they're going to ban you. In general, you should be reviewing your dependencies yourself to make sure it's doing things that you approve of; if you can't do that after Apple has warned you that it's doi…
I think that's being too charitable to Apple. Their review process is automated, and nobody really knows what will trigger the Ban Bot into deleting your account. There is also no apparent way to scan your own app to make sure that you are not in violation of this issue. So you're in a position where the only way to see if you are in compliance is to submit to Apple, but that may result in your account being banned.
While review is automated, I would like to believe that account deletion isn't.
> There is also no apparent way to scan your own app to make sure that you are not in violation of this issue. So you're in a position where the only way to see if you are in compliance is to submit to Apple, but that may result in your account being banned.
They literally tell you the symbols that you're not supposed to use: it's easy to check if your dependencies are using them.
Does anyone use the Mac appstore?
Earlier quoted context omitted.
What's bullshit about banning someone who has been notified that they are in violation of the rules and then tries to hide their use of private APIs rather than stop using them? That's exactly what I would do in Apple's position. Resubmitting the same thing and hoping that it doesn't get caught the next time isn't an honest mistake.
> then tries to hide their use of private APIs rather than stop using them [...] Resubmitting the same thing and hoping that it doesn't get caught the next time isn't an honest mistake. This is missing the point of the post you are replying to. Say you identify five closed API dependencies and remove them. Do you resubmit? If you missed any others, you and all your apps might be banned.
If the APIs didn't exist, then there would be no need for Apple to check and there would be no developers tempted to use anything private.