I used Phonegap to create a mobile app with HTML and Javascript files. I could upload my files to phonegap/apps to create my app online. I did all things well, but BlackBerry requires a signing key and .db file. I have signing keys, as I have the .csi and .csj files.
I tried to get BlackBerry .db file, but how can I get it?.
Apply for signing keys here: http://www.blackberry.com/go/codesigning
You will receive an email with attached signing keys. Follow the instructions in the received email to install these keys and use them to sign your application.
Instructions in these emails will guide you to install these signing keys to your development environment. Upon installation of these keys .db file will be created.
If you experience any problems upon installation of your signing keys contact blackberry support team: http://blackberry.com/support
Related
I have an updated version of an old Xamarin Android app I want to release. I previously set up the signing key which I used to sign the app previously. Apparently, a few months ago I updated to the Google app signing mechanism, but apparently I still need to sign the app myself before uploading. But if I use my old script mechanism, Google tells me "You uploaded an APK that is not signed with the upload certificate." I can't figure out how to set up the signing with whatever that upload certificate is. Neither the Google nor Xamarin docs are comprehensible to me. I downloaded "upload_cert.der" and "deployment_cert.der" files from Google, but have no idea what to do with them. I tried using Visual Studio to publish, but it says to create Oauth client and enter the client ID and secret, pointing to the Google Play Console, but I can't figure out how to do that. It would be really nice if there were some docs for people in my situation.
Somewhere along the way I must have regenerated the keystore, which no longer matched the key Google has. I found a backup of the keystore, restored it, and now it works.
My employer recently entered into an agreement with another company to share the source code for an iOS app that we developed. We haven't yet published this app in the App Store but plan to do so in the future. During the course of development, we've obviously created an app ID, provisioning profiles, certificates for development and remote notifications, etc. all of which are (obviously) tied to my employer's enrollment in the Apple Developer Program (ADP). The app itself is currently configured to allow Xcode to manage signing automatically.
Before we deliver the source code for this app to the other company, I need to make sure that none of my employer's information is present in the project source (so that the other company has to use their own info). I've looked through all the project-related files I could find and the only thing I really saw was a small section in the project.pbxproj file that looks like it is related to signing.
I would guess that this is something that a lot of people who decide to share their source on Github do but I'm still fairly new to iOS/Xcode app development so I was hoping that someone who has dealt with this before could offer some insight? Thanks very much!
If you just want to make sure they cannot get your company's signing identity, you can just send them the project. Since you are using automatic code signing, they would need to have your company's Apple developer ID credentials to sign in to the developer account in order to have Xcode generate a certificate and profile to sign as your company. None of the critical signing files are included in the Xcode project folder.
When you enable automatic code signing and sign into the Apple ID, Scode will generate a certificate and private key, which go into that Mac's Keychain, and a provisioning profile is generated and downloaded, which goes into a specific directory that is common for all projects (https://stackoverflow.com/a/45642752/3708242) and outside of the project directory.
As #Jack states in his answers, there are other pieces of information in the files you might want to scrub, but there is no risk you would be giving them access to your code signing information by sending them the project as is with automatic code signing turned on.
Long story, short, just send them the project directory.
Just clear the bundle identifier in Project->General->Bundle identifier -> set it empty.
For notification other company/Vendor will use there separate certs with respective Apple account.
In every top lines of .swift files there is commented by default code which includes Mac name, you can remove it.
I am a windows user with no access to ios. I am also new to phonegap.
How to add signing keys for ios and certificate in it as i wish to build and run the same.
And how to make our phongap apps public its private now.
Try this link below. It is for how you generate all those certificatesigning, cer, p12, mobileprovision, and pem. Yes, the most important file you need is p12 and mobileprovision. But before you can get those 2, you need to generate certificatesigning,cer, and pem. Remember your app ID and password is important while you generate those file. Don't ever lost it. Later on if you try to upload the IPA file to itunes, you can try appsuploader require to pay for subscription, but cheap price and it is for windows user.
https://www.joshmorony.com/how-to-create-an-ios-provisioning-profile-and-p12-with-windows/
I use this gem to export content in my rails app into an apple pass: https://github.com/frozon/passbook
I have followed all the instructions there but somehow I have issues with the exported .p12 certificate.
When exporting a pass in my app, I always get:
OpenSSL::PKCS12::PKCS12Error in PassbookPassesController#show
PKCS12_parse: mac verify failure
I have used the .p12 certificate of a third party agency before that has developed the rails app. With their certificate it all works fine but mine does not.
I obviously have modified the teamIdentifier and passTypeIdentifier in the pass.json file accordingly. So I also cannot really explain why the .p12 file is working although I have already modified the meta information.
What can be the issue here?
It's an in-house iOS app for a small company. The company has iOS developer enterprise program. I am hoping that it is possible to distribute the app using their corporate website which has an SSL certificate i.e. without using an MDM server.
I am able to export an .ipa file for Enterprise Deployment. Thanks.
You can do it through their server in a few easy steps.
You need to first create an html page which the users can navigate to. This page will hold a button or link which will open a manifest plist with instructions to install the ipa file.
HTML:
itms-services://?action=download-manifest&url="The url where the manifest.plist can be found"
This means that you not only need to generate a .ipa but also a .plist which will be the manifest. You can search how to generate manifest for iOS. One thing to keep in mind, the path to the .ipa referenced in the .plist will need to be its path on the server for example:
https://myserver.com/myapp/app.ipa
For this example we can assume that the myapp/ directory holds the .ipa, .plist and .html file for the app.
Assuming all provisioning profiles are set correctly, the user should then be able to download the app.