Electron apps cannot be submitted to the Apple store
1–10 of 441 posts
Re: Electron apps cannot be submitted to the Apple store
#2Is this an attempt by Apple to increase robustness by reducing dependencies on unsigned binaries?
Re: Electron apps cannot be submitted to the Apple store
#3Well, why the hell is electron/chromium using private APIs? That seems like the real problem here...
Re: Electron apps cannot be submitted to the Apple store
#4Is this an attempt by Apple to increase robustness by reducing dependencies on unsigned binaries?
That is a very specific question.
Re: Electron apps cannot be submitted to the Apple store
#5Good.
Re: Electron apps cannot be submitted to the Apple store
#6Is this an attempt by Apple to increase robustness by reducing dependencies on unsigned binaries?
This is not new. There have been checks for private API usage for as long as I can remember – at least on iOS. It could be the case that there was less enforcement on OSX.
However, this is not really about unsigned binaries. These APIs are from OSX itself. This is about access to private APIs. These have no contract and can be changed at any time, as they were not intended for public consumption.
Re: Electron apps cannot be submitted to the Apple store
#7Tracked over at:
Re: Electron apps cannot be submitted to the Apple store
#8The lesson here is write native apps using the preferred native tools of the platform, and avoid shortcut solutions.
Re: Electron apps cannot be submitted to the Apple store
#9Is this an attempt by Apple to increase robustness by reducing dependencies on unsigned binaries?
No. The symbols mentioned in the rejection are all in signed Apple libraries; the problem is that those symbols aren't part of the public/documented/stable API.
Re: Electron apps cannot be submitted to the Apple store
#10Well, why the hell is electron/chromium using private APIs? That seems like the real problem here...
It's possible electron team isn't even aware chromium is doing that.