New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAS Build rejected with: Apps that use non-public APIs will be rejected #5618
Comments
Thanks for reporting this back, those calls seem to be introduced by Chrome 50, I'll patch them out. |
I have the same rejection
|
@zcbenz do you know when a new release will be made? |
Anyone confirm this fix work for MAS? |
I currently have an app waiting for review. I'll ping here when it's reviewed. |
It got through! Thank you @zcbenz, I believe we have a winner |
@slaskis Awesome, thanks so much for testing the MAS build! |
@slaskis , did you submit a copy of U.S. Encryption Registration (ERN) approval when submitting your app to MAS? As mentioned on this page, it seems we need to do it for all Electron built apps: Cryptographic Algorithms Used by Electron |
@mmm117 actually I don't think we did, we selected "no" the first time and any updates only ask if we changed anything regarding encryption since the last release which we technically didn't :P our app has no network communication though so maybe since we don't actually use TLS they let it pass? but who knows what happens behind the wall of app store reviews... |
My app does use TLS |
I recently read that any app, even native and using apple http libraries, has to answer yes, just for using https |
As I know, France also need this kind of approval, developer need to apply another approval from them if you sell your app in France too.. Good to read: |
slaskis commentedMay 20, 2016
After the entitlement fixes to the MAS builds in Electron 1.1.1 we now got this rejection message:
And after running some commands to try to figure out where the private API:s might come from:
We found that it is to be found in
Electron Framework
:And a quick google search takes us to this chromium code.
I'm guessing there will have to be some update to
libchromiumcontent
which skips these in the case of aMAS_BUILD
?But we're getting closer to be able to get Electron apps up on the App Store!
The text was updated successfully, but these errors were encountered: