We're using Visual Studio Tools for Apache Cordova to build our app for iOS (and Windows).
We have a Mac running the remote agent. This works well, except we've only been able to have the setup produce signed .ipa files.
We're now looking into being able to create an unsigned "app" that we can deliver to our customer. They will then sign it with their enterprise certificate and distribute it within their orgainization (not the App Store).
The recommended way to deliver the app to the customer seems to be to create an xcarchive (I have looked at the option to deliver an ipa signed with our develoepr cert and then have the customer resign it with iReSign, but that seems flaky).
Is there a way to do that with this setup without any manual steps on the Mac?
Any pointers in the right direction would be much appreciated.
As far as i have analyzed, the easiest way to create an xcarchive is to use cocoon cloud service. Infact, it does gives the flexibility of generating both xcarchive and IPA.
Also you have full control of your build process as it provides various config controls and it is already used by some renowned companies.Suggest to have a look at cocoon platform once.
I know you have mentioned that you cannot rely on 3rd party service but it is the easiest approach as far as i my analysis. Also it may be useful for someone who is struck with a similar issue to give it a shot.
I am creating a free iOS applications. I want to make clients to be able to download new version of my application from setting page of my app by pressing a button named download new version.
I had see this accepted answer that looks good for me:
https://stackoverflow.com/a/23561783/1939409
Actually I am wondering whether this solution only works for ad-hoc apps or I can use BetaBuilder to create a IPA for my final apps that should install on non jailbreak devices too?
Also is there a way that I call this URL from my app with objective-c codes so that app itself download the IPA file and install it on the device?
You can update app by providing link of app's new version only if you have generated ad-hoc or enterprise distribution build. Also your app can not download the new version on its own. You need to open browser with new version link and rest of the process will be handled by iOS.
I am interested in developing an app for BlackBerry devices, and was wondering if they support the concept of demo or beta releases for their app developers? By this, I mean the ability to deploy a beta or demo version of my app to a limited/restricted audience, such as business partners, customers, external beta testers, etc. Nothing in their Testing and Deployment documentation indicates either way. Thanks in advance!
There isn't a built in beta process in App World for BlackBerry 10, but you can share the debug version of your app with your beta participants. When you create a debug token, you specify which PINs you want it to be valid for. The debug token will only install on a device with one of those PINs, and your app will only install on a device with your debug token on it. The token will only be valid for 30 days. You would have to deploy it with the command line tools and not App World.
This link on the BlackBerry Developer blog explains how to do it: http://devblog.blackberry.com/2012/04/debug-token/
It's for PlayBook, but the same process applies for BlackBerry 10 as well.
I actually don't know if RIM themselves have anything formal, but since I've always released BlackBerry apps on more than just the official App World store, I've used a beta testing system that is independent of RIM. Luckily, the legacy BlackBerry Java platform gives you the freedom to do this, free of charge. (Note that this answer is not about the upcoming BB10 platform!)
Over-the-Air (OTA) Installation
You can have your beta testers install your beta versions, Over-The-Air (OTA). Unlike iOS, for example, you aren't limited to a certain number of test devices, and you don't have to tell RIM what the unique identifiers of all the test devices are.
So, what I do is just put beta versions of my apps on a webserver, and send links to beta testers that allows them to download them. So, you are in control of who gets access. If you need security to limit the beta version to nobody except the official beta testers, then you are certainly free to add password protected logins to your webserver. That works the same way it would for any other secure web content.
If you do this (OTA), here are a few references:
http://www.blackberryinsight.com/2008/07/08/howto-setup-an-apache-webserver-to-deliver-blackberry-ota-applications/
Blackberry over the air installation
https://stackoverflow.com/a/10307074/119114
There are a couple steps to be aware of:
You normally just upload a .cod file to BlackBerry App World. If you want to deploy an app to your own webserver, you also need the .jad file. A JAD file is basically just a descriptor of the app, that can redirect a BlackBerry browser to the .cod file for installation. Your build process is already probably generating the .jad file for you, in the same output directory where it generates your .cod files.
You may need to configure your webserver to properly setup MIME types for files with a .jad extension. If you use Apache, then this is what you would put in your httpd.conf file:
AddType text/vnd.sun.j2me.app-descriptor jad
you may also need to add a MIME type definition for the .cod type, too
AddType application/vnd.rim.cod .cod
If you don't have access to the web server's httpd.conf file, but can place the JAD and COD in your own user directory, then you can configure the MIME types in a local .htaccess file.
Depending on your web server configuration, there may be a couple more steps necessary. Check the OTA links I provided above.
Desktop Installation
Another option is to simply email your beta versions to beta testers, and have them install on their devices using BlackBerry Desktop Software. I don't do this, but it is another way to accomplish the same thing. For this, you use the .cod file, and also the .alx file, which is also generated by the normal BlackBerry build process.
Note that some of the project properties that get put into the .alx or .jad files are things that you don't need to worry about if you only deploy the .cod file directly to BlackBerry App World. If you use one of the options (ALX for Desktop installation, or JAD for OTA), then I would recommend opening up the .alx or .jad file and just inspecting the values for correctness. They're normal text files, and most of the values should be self-explanatory. I believe all settings can be configured from inside your IDE. If you use the BlackBerry Eclipse plugin, right click on your project, select Properties and look around there.
Here are the official RIM docs on all your installation options
its not possible. When you publish your app in app world, it will be available to all users. So you cant set any special conditions like- available only to some people. Else make it in un published mode. Then only users with sandbox id can access your app.
Check the below link for BB 10 Cascades beta 3 release(Preferrable way of development in BB 10)
https://developer.blackberry.com/cascades/
For BB 10,they are plenty of ways for developing the applications ,check the below link
https://developer.blackberry.com/platforms/
Currently I use Ripple "Package and Sign" option, and then use Blackberry Desktop Manager (with my blackberry connected to PC via USB) to import then apply the app. What annoys me is the whole process takes min 10mins sometimes 30mins all up.
I try to skip the "Sign" option, ie use "Package" only but when running the app from the device it gives me this error: "Error starting X: Module 'X' attempts to access a secure API".
Questions:
How are you installing the app on blackberry during Dev/Test?
How are you distributing the app for PROD release?
I have heard we can distribute via Wi-Fi or just sending someone a link to download the app, but cant really find much info on it. Any help?
You have to sign Webworks apps that you intend to use on the phone. Test as much as you can in the simulator, since it has the fastest turn around time between compiling and running the application.
Appworld is probably going to be your easiest distribution method if you intend on having users buy your app.
If you want to use the internet/WiFi option, you'll need to have a webserver/site you can upload all the *.cod and *.jad files that are built when you package the app. Then point the people downloading the app to the .jad file and their phone will try to install it for them.
I got the signature keys from the blackberry web signer. All the keys in to one folder.
I developed my blackberry application using eclipse plugin 1.0.
First I am go to Blackberry->Install Signatures keys and select the .csi key files but there is nothing happened.
So I double click the key values and register the keys. Register keys successfully.
Then copied the three key values in component package bin folder. Then go to eclipse plugin blackberry and select the request signatures. Nothing happened.
How to sign my application? Please do help me for sign the application.
Have a look at the "How_And_When_To_Sign_V2.pdf" attachment on this website:
http://supportforums.blackberry.com/t5/Testing-and-Deployment/How-and-When-to-Sign/ta-p/442779