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
Related
i explain my problem.
We are two applications with the same name "MyApp" currently created on the itunes connect dashboard.
We did able to create two application with the same name using a different language localization (one in english and the other in native italian). Over this, applications are distributed to different countries (so the swiss - aka ch - version won't be visible to the italian - aka it - users).
Problem Context
The problem is related to the application upload: i'm using the Application Loader software to upload the respective ipa (myapp.1.0.9.prod.it.ipa and myapp.1.0.9.prod.it.ipa) to their remote application project dashboards.
What's wrong?
When i'm publishing the app for ch (myapp.1.0.9.prod.ch.ipa) and the process end correctly, if i open the TestFlight tab for the ch app, i'm not able to see my build but instead, it's result available for the it version.
How we distinguish apps in the project
To distinguish rightly the application, we performing a general renaming of the package name inside all project files to aim this situation:
myapp.1.0.9.prod.ch.ipa with package name "com.myapp.domain.ch"
myapp.1.0.9.prod.it.ipa with package name "com.myapp.domain" (considered as default)
Goals
Publish current ipad downloaded to its app project.
Limits
Please don't provide me solution that include itunes with the Archive menu, we cannot do it manually due to a builder dependencies that will be very pedantic without builder's feature.
Thanks in advance for your help!!!
Simon
You mention that you are changing the package name. I'm not exactly sure what you mean by that but you have to be sure you are setting the correct Bundle Identifier, or CFBundleIdentifier in your Info.plist to make your ipa upload to the correct iTunes Connect application.
Can you take a peek inside your generated .ipa and make sure you have the Bundle Identifier set as you expect?
I'm specifically looking to see if SugarWod has implemented a Custom Url, and if so, what it is. They have no developer documentation available and their support has yet to respond back.
If that's unknown, is there a list of sites that currently implement a Custom Url, so that another iOS app can open it?
Or is there a way to see find the Custom Url of an app, if it exists, from your device, iTunes, etc?
Thanks a lot.
It supports a custom URL which starts with sugarwod://
You can easily find this out for any app you have the IPA file of.
1. Rename the extension of the app from .ipa to .zip
2. Extract the zip file
3. Go to the Payload folder of the app
4. Right click on the single file there and choose "show package contents"
5. Open the Info.plist in Xcode and look for the URL types
If there are supported URL's, they can be found there.
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/
I want to use PhoneGap to sign my BlackBerry App. When I go to add the key files it asks for a CSK file.
I went to https://www.blackberry.com/SignedKeys/ and requested keys.
However the files sent to me were 3 different CSI files(RBB, RCR, RRT).
How and where can I get the CSK and DB file needed to sign apps on PhoneGap?
First you need to install the blackberry SDK (as part of Eclipse if you're using this IDE, otherwise get the standalone java one).
Then follow these steps.
Basically this will store your key locally, then you create a backup of it in the form of a .csk+.db files.
Adobe® PhoneGap™ Build currently provides a default BlackBerry development version for all users, which provides an Over-The-Air install for your PhoneGap applications. However, to distribute your own BlackBerry applications, you will need to register with RIM for your own keys, and then import those keys into PhoneGap Build.
To register, fill out the form on RIM's site , and, once you receive your keys, follow the installation process locally.. using the steps mentioned here
Gurus, I got the keys from RIM to sign my application, however, the signing tool won't sign the RRT, I'm succesfully signing the RCR but not the RRT so the application won't run on a device, I'm getting this error that speaks for it's self:
alt text http://www.techlocus.com/blackberry/problem.png
I'm using Eclipse with the plugin 1.1. JRE 5.0.0.
Any help would be appreciated, if you need more information please let me know
Thanks in advance!
RIM sends back your signing keys as three separate emails (RCR, RRT, and RBB) - make sure that you clicked on the attachment for all three of them to register them on your computer.