Verification error on running blackberry application - eclipse

I am working on a blackberry application that was developed by someone else. I tried creating and running other applications. All the applications work except this specific one.
For this application I need the secure element signatures. I got signature keys from blackberry and I requested the secure element signatures.
Whenever I run the application on a simulator it works perfectly. However when I try to run it on Blackberry Bold 9900, it tells me 'application name' has verification errors and sometimes it says application terminated and other times it says 'net_rim_tsm_lib' not found.. Currently it says 'net_rim_tsm_lib' not found.
I am not sure what is wrong with it. Please help.
Thank you in advance,

After searching the web and asking co-workers, I found out what was the problem. Basically, I was trying to use the secure element and the signing keys given to me by BlackBerry do not have permission to use the secure element. For my purpose, I do not need to access the secure element so I just took that part of the application out and it worked fine. However if you need to access the secure element, then you need to get the signing keys for the secure element. You can ask for them from BlackBerry, my request was not approved so I was not able to get the signing keys. Good luck with getting them.
Just a note, while searching over the web I found many reasons for the verification error. I am not sure if all of that is just BS and the whole reason behind the verification error is just some signing keys. So I am not sure if this is true for all of your issues.
Thanks

Related

accessing iOS device SSL certificate

We are developing an iPhone app, and we have one client who wants to use their own SSL certificate bundle. As far as I know this is not possible since the app can't access the device cert (assuming the client just install their own bundles on each of their device). Other option is to submit a whole different app just for them, but that's not a good solution and I am trying to avoid that.
Does anyone have experience with this sorts of problems? I tried to google around but could not find anything.
Any help or direction would be much appreciated!

The relationship between Provisioning Profiles, Certificates, App IDs, and Keys

Right now I'm just trying to test my app on my phone and not deploy to the store.
How are all these things related? Since I'm not trying to upload to the store, can I ignore any of them?
I'm on the University Developer program. I was able to get a certificate and install it in Xcode, but builds still fail.
Is solving this problem just a matter of changing the application identifier? How do I know what to put in?
One thing I noticed is that in the Developer Portal I see only one App ID but it's for someone with a different name. So I guess I don't have an App ID. Do I need one if I'm just trying to test on my phone? If I need one, then how do I get it?
Help! It seems the more I research these things the more confused I get. If you can't solve my problem, can you at least tell me how these things are related to each other?
Provision Profiles are a very long, unique, string that allows the device to recognize certificates (very VERY helpful for development).
You must provision your device with the specific bundle ID of your app (done through developer.apple.com), then install said profile in order to even think about building with a valid certificate. However, it is much easier to have Xcode generate a wildcard provisioning profile, which allows you to test ANY bundle ID (it shows up as *.mobileprovision).
Certificates are the other side of the coin. A certificate for anything (website, application) indicates that this service can be trusted by the user, and more importantly, the OS. Certificates are issued by Apple California, are valid for a year, and may be revoked at any time for any reason. On a closed and secure platform like the iPhone, a certificate is a must for any application.

Install SSL Certificate straight from the App

I've a trouble finding it in documentation. So the thing is simple. I'd like to install the SSL certificate in order to communicate with the server. That's very typical if you browse the site and you have the warning about the certificate and you can accept it or not.
On the iPhone, while using safari it usually takes user to the settings with preloaded screen asking my to install the certificate.
The thing is I want to use the certificate to communicate with the server on production version. And there will be no browser, but typical table loading the rows from the XML/JSON etc. I don't want to tell the code to generally allow untrusted certificates. I just want to preinstall that one, either by user acceptance or without it if not necessary.
I know the workaround to simply mail the certificate as an attachment, but c'mon, I'm not going to display the screen about this during my application launch.
Thank you in advance
Chris
This should be done via Keychain Services, check documentation at developer.apple.com.
Have a look at the AdvancedURLConnections example from Apple as suggested in this answer.
If possible, I would avoid the hassle and just get a valid certificate signed by a trusted CA.

I'm in an iPhone provisioning mess -- Insight needed

My app has been more or less ready to be submitted for a while now, but as usual, the overly complex provisioning nonsense that Apple forces developers to jump through is causing me an enormous amount of stress. Initially the problem I was receiving was Invalid Codesign. After trying every 'solution' i could find on the internet and failing, I decided that it would be best if I started fresh -- Deleted all my provioning profiles, cleaned up my itunes connect account, deleted all my keys and certificate from the keychain access and started from scratch. The problem is that once I deleted by keys and developer certificate from the keychain access, I cant get them back!!! I've tried restarting, I've tried installing it every way imaginable, but I just cant get anything to be listed in the 'keys' nor 'my certificates' sections of the keychain access. I do have an iPhone edveloper profile in the 'certificates section' but this doesnt even seem to be of any use because when I look in the Organizer there are no developer profiles listed, and all my provisioning profiles warn "A valid signing identity matching this profile could not be found in your keychain"
Someone please help me through this mess. I've been developing my app for several months now and I already have an app in the App Store but Apple insists on making this process damn near impossible. Thanks so much!!!
Your public and private keys are automagically generated when required - if you use the certificate assistant to request a signing certificate as the provisioning profile describes you will find your new private/public keys created.
Once you begin this process you should also use spotlight to remove all .mobileprovision and .cer files you may have remaining in downloads, and also use organizer to remove profiles from devices. If you are starting from scratch you want to make sure none of that stuff remains to cause you problems.
This is an overcomplicated process to be sure, but once everything is really deleted and a fresh start is made it should be good for some time. The biggest problems I have had are when getting a new Mac and having hiccups with exporting/importing keys in an effort to keep my old certificates/provisioning valid.

Program for iphone push notifications

I'm trying to send push notifications to an app. The program, PushMeBaby, which a co-worker of mine used does not seem to work anymore. I get an -909 error from the SSLwrite command. I couldn't figure out the meaning of it.
Does anyone know a good tool/program that sends push notifications to the APNs-server?
or has anyone know, what the error code means?
Yours
Bujtor
Well... as it turns out the problem was the certificate.
Apparently it's not that easy to get the correct and valid push-certificate. My boss's third attempt succeeded. The Certificate Signing Request had to be made using the MAC i'm working on, where PushMeBaby is running. Otherwise there was no private key associated with the certificate. In addition the provisioning profil had to be made to only work for that one application.
I hope it helps others having the same problem.