-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
0.13 MAS-ready on launch? #4556
Comments
CC @alexeyst who worked on this. Would you mind to check whether the current RC version MAS compatible? Thanks. |
@rogerwang @alexeyst any new developments on this? all related issues are from 2015 and apply only to 0.12 |
Sub-tasks for MAS support:
|
@ghostoy Wow, great work and super-fast too!! :))) can't wait to check out the MAS build flavor 👍 💯 |
@haraldox Here is the test build for MAS flavor you can try with http://dl.nwjs.io/live-build/05-09-2016/nw14-df7f7cf-723666b-756e507-5a26102. There is also a reference script for signing the app in https://github.com/ghostoy/nw.js/tree/nw14-mas/tools/mas. Would you please try wit this version and give us feedback? :) |
I'm getting this message when verifying the signing with spctl -a -vvvv "$app" This is after copying my app to app.nw and then running the signing script. |
@jpittner I can't reproduce the error with |
@ghostoy if I just copy the nwjs.app from the zip file, throw that into src/ and don't change the Info.plist, and don't add the app.nw, spctl fails with error rejected (with no details provided. apparently Apple doesn't understand what verbose means) I then take the Info.plist from nwjs.app and change the bundle identifier to com.me.myapp, CFBundleDisplayName to myapp. I copy the app.nw to the proper directory and then sign. This results in the error "a sealed resource is missing or invalid". |
@jpittner The signing script will properly change all the bundle identifiers and versions with the given parameters for your app. Or you have to change all the plist files nested in the app, including the framework and helper. As for the "rejected" status, since your app is not on Mac App Store yet, your certificate will be rejected by |
@jpittner @haraldox @gpetrov We have announced the alpha testing for MAS build of 0.14.4 in the mailing list recently. If you have any problem using MAS build for NW.js 0.14.4, please send your further feedback here. Once it's confirmed that Apple accepts the NW.js based app, we will finish alpha testing and release beta versions of MAS builds for LTS (0.14.x) and stable versions. |
@ghostoy We would really like to try the MAS right now, but our app requires File/Folder permissions outside the App Container. So we need to ask the user for permissions according to Apple guidelines. |
Yes, it's automatically done through |
@ghostoy that's awesome! Does it work for folder picking as well? And are the authorizations saved even if the app restarts afterwards? So that it has a lifetime authorization? |
@gpetrov Yes, it works for folder picking. NW.js uses the standard |
Is there an approximate timeline for this feature? We have an app ported from MacGap to nwjs waiting for a stable MAS version. |
The MAS build here can be successfully uploaded. But we are unable to anku94 notifications@github.com于2016年7月11日周一 18:45写道:
|
@anku94 Could you help to test if alpha build can be published to App Store? |
Hey, sorry for the delayed reply. Will try it over the weekend and let you |
@anku94 Did you get approval from App Store? |
@gpetrov Sure. |
@ghostoy i wonder what is the progress on including MAS builds in published builds and live builds? As i understand, there is only one MAS build published for now. Thank you and all participants for the great job! 👍 |
Beta release based on 0.19.5 is available in http://dl.nwjs.io/v0.19.5-mas-beta/. Please follow the document of Support for Mac App Store for the signing process and usage of the signing scripts. |
My app passed review successfully, thus confirming that v0.19.5 mas build and signing script works fine. Thank you @ghostoy and nwjs team. |
Look forward to seeing it with published builds, will be easier to automate the whole process with nw-builder. |
@chino23 @rogerwang Any update on 0.20.x builds? |
CC @sunlin-link who own this branch now. |
@rogerwang will there be a 0.26.x Build for MAS ? |
@DrDoing good to know the old version is working for you. @sunlin-link has been working on a new version of MAS build. He will report here if there is any progress. |
any news about a new MAS build ? |
@sunlin-link please advise. Last time I heard from you it's said to be "nearly done". |
I've already finished rebasing to lastest stable release and am working on a final crash issue. |
ping |
@sunlin-link how is the progress with the latest NWJS build as MAS? We really need it to publish our app to the Mac Store. |
@gpetrov same situation here. My app is published on macupdate and our webpage, but it would be great if we can put it on the official app store! |
Is this still being maintained or not? I have so many issues with a regular nwjs build since the mas version is just too old to use: https://groups.google.com/forum/#!topic/nwjs-general/EE8eYlG3XgE |
@sadikyalcin NW.js is being actively maintained. But I don't think the Mac App Store version is, which is a shame. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi there!
Huge thanks to @rogerwang & team & collaborators (& Intel for sponsoring) for their efforts on
nw.js
0.13!! => Looking so much forward to Launch Day :)We are currently developing in parallel for Electron and nw.js (as cross-compatible Chrome App) and need to know how this will play out with Apple's Mac App Store requirements and review process in the near future! to make a decision about which "container" to use for our release...
We are currently only aware of Audio & Video Playback licensing issues resulting in Apple not allowing such apps in Mac App Store (ffmpeg). See this issue for details.
On a technical sidenote: According to @johansatge's nwjs-macappstore-builder and this comment , is ready for 0.13
Does anyone have any recent experiences with this?
The text was updated successfully, but these errors were encountered: