I have developed a hybrid application for Windows 8.1 that I want to submit to the app store. As the app package requirements, it does not look at like I need to sign my package using any a trusted certificate.
http://msdn.microsoft.com/en-us/library/windows/apps/hh694075.aspx
I am using VS 2013 to create my project and my app package. Is the default certificate enough ?
Can some one who has submitted apps for approval, please speak about their experience regarding the app signing and if/how one can get this certificate.
Answering my own question, I was able to submit the app. I was able to sign the app once I linked my store account.
Related
I have an Ionic application, which is currently deployed to the Apple and Android stores. I Now wish to deploy to the Windows store. I have Visual Studio 2015 and have built running the Ionic CLI. I see a lot of created files, including a CordovaApp.Windows10_1.0.0.43_x86.appx
For iOS, the signing is handled via the xcode / developers console, and for Android I created using the keytool which is part of the JDK. Now for Windows..
I have found this on certificates, and this on signing.
I just want to see if I have this understanding correct before I do anything.... so unlike the iOS and Android, where I can just sign, with no extra cost, for the UWP, you actually need to purchase a certificate, just like you do for SSL, to use for the signing of a UWP? Also the app uses SSL (makes https calls to a server via SSL) - not sure if this makes any difference to the certificate required (as when I ran in debug, the https call seemed to be blocked).
Thanks in advance for any information!
I just want to see if I have this understanding correct before I do anything.... so unlike the iOS and Android, where I can just sign, with no extra cost, for the UWP, you actually need to purchase a certificate, just like you do for SSL, to use for the signing of a UWP?
No, you don't need to purchase an certificate to publish your app to store. You only need to create a certificate for package signing, for details, please refer to Create a certificate for package signing. Then you can sign your app using SignTool, please refer to Sign an app package using SignTool.
After that, when you are submitting your app, you will need to have a developer account, which requires some monetary cost,
I'm having some serious trouble signing an application for ad-hoc distribution. Is it possible to distribute an app with the following requirements?:
Does not require tester to provide UUID up front
Outside app store
Utilizes entitlements such as VPN or Keychain Sharing
I ask because exporting without signing (Organizer (select archive) > Export > Export as Mac Application) fails with "embedded provisioning profile not valid: ..." on some devices. It appears to work on others though.
Thank you!
If you're trying to use the NetworkExtension framework (which I'm assuming because you tagged your question with nevpnmanager,) unfortunately that's only available in App Store apps.
I know this because I asked Apple. I was trying to make a non App Store NEVPN app, but no dice. Quinn from Developer Tech Support told me the NEVPN stuff is only available for App Store apps, and that I should file a bug report (which I think I did.)
We are developing an application for our client and he wanted us to build App so he can publish the app over the Mac App store,
As of now we don't have Mac Developer Id, and we have received App Id from the client,
My question is, is it possible to make build only using App Id ?
I guess with App ID you mean something like "com.company.product".
Getting an Application for OS X to the App store is not an easy task (compared to iPhone/iPad).
To sign the App you need the public/private Key pair and a couple of certificates from your client.
The convenient way to upload the app to apple is done using Xcode.
Does the client use Xcode? If your client uses Xcode, then your client can do all the signing stuff. Then your client needs just the source code.
If your client needs a signed binary, then it's not obvious HOW he gets the app to the Appstore. There is a tool which can be used to upload the binary: "Application Loader.app"
(Here is a similar SO question which describes the toolchain: How to submit an iOS app WITHOUT XCode?)
If you need to deliver your results to your client as a signed bundle then you need all Certificates from the client. Your code must have all entitlements set. Uploading this code without testing your entitlements on your local machine is like driving a car blindfolded.
However: If you need to deliver a signed binary to your client, then you need all certificates.
If you will distribute the code to the client, it's not a problem delivering an unsigned binary to the client. Apps can be executed without code signing. Even without an valid AppID your code may be executed.
If your client has knowledge about Mac development, this should be no problem. If your client't doesn't know anything about Mac development, you should get access to his Mac-Developer account and do it for him.
Conclusion: The AppID is just a string to identify the app. If your client does the code signing stuff and uploading to Apple by himself using Xcode, then you need nothing else.
If you should use iCloud or App-Sandboxing (Entitlements) then you NEED certificates from your client.
I need to build an application for Lion with iCloud functionality.
I know that I have to sign the application in order to use entitlements options to enable iCloud.
I do NOT have to distribute my application on MacStore, just to sell it directly to my clients.
Do I need to subscribe to Mac Developer program in order to get a working certificate? Or I can generate a self-signed one and use it to sign my application?
Thanks
Currently it looks like you have to sign up to the Mac Dev Programme to be able to support iCloud in your apps (you need to edit a setting in the portal to enable iCloud for your bundle ID).
Additionally, it is unclear if non-appstore apps will be able to support iCloud anyway.
I started some days ago a small Mac app for Mac OS X Lion. I've never uploaded a Mac app before, so this is the very first time.
This is what I've already done:
Created App ID
Created Certificate
Installed Certificate
Created a Production Provisioning Profile
Changed the App ID to my generated one
Created a new Configuration based on "Release"
Changed its Code Signing to 3rd Party Mac Developer Application
Selected the "Production"-Configuration which I created for the Archive-Scheme
Archived the Application
Now I wanted to "Share" the Application. Xcode (4.1 btw) said to me, there were no valid signing identities. Does I need to add an Entitlement.plist like in iOS? Have I forgotten something?
Update:
I just figured out, that I have to sign my app twice. I've still selected "3rd Party Mac Developer Application" but I can't select the Installer cert while submitting my app.
Have you installed the WWDR intermediate certificate? I just had the exact same problems and my issue was that the intermediate certificate was not installed on my machine. Granted, nowhere does Apple explicitly say you need it installed, more like suggestions. But, you do need it. You can find it here, or by going to Developer Certificate Utility under the Mac Developer Center.
I got it to work. I deleted my App and created it new.
I didn't create a new Configuration, and I only changed the Code Signing Indentity of the Target to 3rd Party Mac Developer Application. After this, I archived the app and then I was able to select the installer cert.