Live data from Hacker News

Electron apps cannot be submitted to the Apple store

david.dev

81–90 of 441 posts

Re: Electron apps cannot be submitted to the Apple store

#81
post #8

The lesson here is write native apps using the preferred native tools of the platform, and avoid shortcut solutions.

I think this is a really elitist and unsympathetic statement. It completely ignores the fact that there are people out there whose only realistic option if they want to release on multiple platforms is to use something like electron. You can preach native all day long but the reality is that some people simply do not have the time (i.e. money) to learn, build and maintain three completely different systems and architectures and at the same time and also build a product. Are you saying that these people should simply give up because you consider it a "shortcut solution"?

Yes electron comes with some overhead. But what you get from paying that price are products that otherwise likely wouldn't exist. Some of these are bad indeed, but some of them are also really good and provide real value.

Re: Electron apps cannot be submitted to the Apple store

#82
post #48

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.

Presumably you can't check for violation yourself without submitting.

You can, and the rejection email even provides instructions for how to do so.

Re: Electron apps cannot be submitted to the Apple store

#83
post #21

Putting it together: This is about submitting an app to the Mac App Store. Apple has had a requirement that apps not use private APIs for a while. It sounds like Chromium, and hence Electron have had references to some private APIs for a while, but Apple has only recently started enforcing their requirement. (Or perhaps only recently started scanning for these particular APIs.) It’s a little painful for the developer…

it seems that the scanning started these days. I had an app build a week ago and I didn't have any API error in the rejection.

Re: Electron apps cannot be submitted to the Apple store

#84
post #21

Putting it together: This is about submitting an app to the Mac App Store. Apple has had a requirement that apps not use private APIs for a while. It sounds like Chromium, and hence Electron have had references to some private APIs for a while, but Apple has only recently started enforcing their requirement. (Or perhaps only recently started scanning for these particular APIs.) It’s a little painful for the developer…

[deleted]

Re: Electron apps cannot be submitted to the Apple store

#85
post #61

> I did write back to Apple trying to explain that I am using Electron and I can't really change any of these public-framework usage Yeah. So? By linking a framework that's using private APIs, this becomes your problem now. And Electron's problem, by extension. Go bug them, not Apple.

How short are memories. I remember how Microsoft was vilified for supposedly having secret Windows APIs that allowed Microsoft apps to get better performance. That was mostly made up and even if such APIs existed, any program could have used it. Even at the height of corporate arrogance Microsoft didn't dream of banning developers for using undocumented APIs. Apple seems intent on becoming more evil than Microsoft ev…

Undocumented APIs get broken. That's a big problem for user experience, particularly if it happens to be being done by a framework relied upon by a very high percentage of app use. Seems pretty fair imo

Re: Electron apps cannot be submitted to the Apple store

#86

Earlier quoted context omitted.

This summarizes Apple's attitude to developers. Eventually, you'll run foul of some obscure nonsensical Apple policy, and Apple will not hesitate to show you the finger. And Shame you for your dev choices.

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.

Re: Electron apps cannot be submitted to the Apple store

#87

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.

Huh? The problem isn't that the developer itself is trying to cover his misbehavior, but the fact that the developer can get banned for something out of his control.

There's nothing out of the developer's control about what they submit to the app store.

Re: Electron apps cannot be submitted to the Apple store

#88

The basic concept isn't too disturbing; Apple packages private APIs that have no guaranteed behavior or expectation of support. If you depend on those APIs, it's very possible that your app will break in a future OS update. This is conceptually no different than calling something in the sun.* packages in Java. For years it was ok, and then ... it wasn't. This, however, is draconian: > Continuing to use or conceal non…

> "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.

Re: Electron apps cannot be submitted to the Apple store

#89

Why doesn't Apple change their SDK to make the public APIs non linkable?

Because they need to link against these symbols themselves. They have used TAPI in the past to keep these symbols out of the public SDK, but it's quite easy to make your own TBD that lets you link against them anyways. (By the way, you posted your comment twice.)

Re: Electron apps cannot be submitted to the Apple store

#90
post #61

> I did write back to Apple trying to explain that I am using Electron and I can't really change any of these public-framework usage Yeah. So? By linking a framework that's using private APIs, this becomes your problem now. And Electron's problem, by extension. Go bug them, not Apple.

How short are memories. I remember how Microsoft was vilified for supposedly having secret Windows APIs that allowed Microsoft apps to get better performance. That was mostly made up and even if such APIs existed, any program could have used it. Even at the height of corporate arrogance Microsoft didn't dream of banning developers for using undocumented APIs. Apple seems intent on becoming more evil than Microsoft ev…

Microsoft didn't ban anyone for using undocumented private APIs because they couldn't, not because they chose not to.

Apple, or Microsoft for that matter, would do the same thing here, because the locked down platform is more valuable/profitable then an open platform.

Developed for Android - at least you can have your app sideloaded if the platform owner decided to remote you.

Or better, make your app a progressive web app. Don't use hardware api not available to the browser and you cannot be removed!

Post reply on HN