Is it necessary to sign every blackberry application even if i have to just test it on blackberry real device? - eclipse

I had only packaged my application for Blackberry using ripple, but didn't sign that. But when I tried to run the application on my device, it is throwing an error message like Module Mybbapp attempts to access a secure API and the application terminates.
I am using Ripple version 0.9.16 and Blackberry SDK 2.3.1.5 using Eclipse.

If you are using signed API in your code, then you need to sign your application, before installing it on an actual device. Unsigned app that uses signed API will work only on simulator, but won't work on an actual device.
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.

Related

Internal testing build doesn't authenticate with google play games

App is developed in Unity. The .apk if shared externally works and im able to sign in with GPGS. However the internal testing build downloaded from Play Store wont let me authenticate. I rolled out the internal testing with all the terms and service accepted. I selected the email-list of testers as well. No idea why it works on a externally shared .apk but not when downloaded through google play tester link. Only think I have done so far is disable billing for the app though I have 300$ worth of credit due to first sign in. Since it works outside of playstore download I assume the billing isn't the problem?
I rolled out the internal testing with everything set. I was expecting it to sign in with GPGS properly as it does when the app installed via externally shared .apk file.

Install Multiple Blackberry WebWorks SDK's With Signing

I am trying to install the Blackberry 10 SDK as well as the PlayBook SDK for Blackberry and can't get the signing to work. I set up the signing and registered the keys for the Blackberry 10 SDK no problem. I then installed the Blackberry PlayBook SDK and then tried to register the keys for it also. I tried to register the same keys as for the BB10 SDK and new keys just for the PB SDK and in both cases I get the error "Error: Already registered with RDK". When I build the BB10 app it works okay and builds the app with signing. When I try to build the PB app I get the message "Cannon sign the application - failed to find signing keys".
I have read through the documentation and I can't see anywhere on how to set up signing with multiple SDK's on one machine. I am sure this can be done, but can't seem to figure out how it should be done to get the singing working.
SDK's:
BB10-WebWorks-SDK_1.0.4.11
WebWorks-Tablet-Win-v2.2
OS: Windows 8
You do not need to register code signing keys more than once.
When you were emailed the *.csj files from BlackBerry, you installed them on your machine using these instructions:
https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html
Doing so generates *.p12 and *.db and *.csk files in the following folder:
%HOMEPATH%\Local Settings\Application Data\Research In Motion
Both the BB10 and PlayBook WebWorks SDK should be able to re-use these files for signing. If they cannot find the signing keys, I suspect your system has the %HOMEPATH% variable set to the wrong location.
Try installing both SDKs to the same /Program Files folder and make sure that %HOMEPATH% is correct.

Application failed codesign verification, iPhone

I have made an app for the iPhone using flash CS 5.5, tested it on a device (it works fine on there) and I'm member of the development programme. I'm attempting to upload the app to the store after filling in all the information on iTunes connect. However, when I attempt to upload the ipa file through the Application Loader (Version 2.5.2) I keep encountering the same error:
'Application failed code sign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.'
I've tried creating the certificates again but still getting the same error.
Thanks for any help :)
It means that you are not using iPhone Distribution Certificate, which is required to upload apps on the app store. I'm guessing you are using a developer certificate.
Here is link how to create distribution certificate for app store submission: Steps to create a distribtution certificate.
Next time do a search you'll get plenty questions related to this topic. For example:
Application failed codesign verification?
Try again with your release certificates, and make sure that whatever you are quoting there for making the certificate should be same as you app's plist file.
Refer to this links: Building Your App for Distribution

Code sign Error

I have created a new iPhone application.I have two mach machines. I have created the certificate for running application in iPhone in one mac. Can I use the other mac for running the application in iPhone. But when I try to do so I get an error "Codesign error:Code signing is required for product type "Application" in SDK Device iPhone OS 3.1.2. Please some one help me.
Regards,
krishnan.
Have you transferred your credentials to the second Mac? They are stored in your keychain.
You may need to read up on how Code-signing works: http://en.wikipedia.org/wiki/Code_signing
Here's an overview:
Developer creates a Certificate via a Certificate Authority (CA)
This certificate is used to 'sign' the binary, providing 'proof' of who created it
Developer then uses the Certificate to sign the binary (this is the step you're missing on the second MAC)
This is handled via xcode, assuming you've followed the detailed steps on http://developer.apple.com/iphone
Clients using the binary can now verify the Certificate against a known CA to ensure the integrity of the build.
Also check that you are code signing on the target as well when you do the Archive build
Spent hours to figure this out. Actually you need to click on Project --> Build Settings --> click target --> code sign..
THIS IS not apparent

Deploy midlet on Nokia mobile

I have written a midlet which asks username and password and connect to servlet running on tomcat to validate. When I run the midlet on the emulator provided by sun toolkit, first time it asks "This midlet wants to connect to http://... using airtime" and asks user permission. I want to know is there anyway to get rid of this? Once this app is installed on a real mobile would it ask user permission every time when application starts or it can be set at installation time?
Secondly how do I deploy my midlet jar on Nokia E65?
I used the Nokia software came along with the cellphone to deploy my application on handset. Whenever I start the application, first time it asks me "This midlet wants to connect to http://... using airtime"
Ad first: You need to setup proper security permissions for your midlet and secondly you will need to sign it with some kind of certificate the device trusts. This is easy for the emulator where you can create self-signed CA and import into the emulator key-store. For real devices you will probably need some commercial (paid) certificate.
Ad second: You will probably need to make the midlet JaD/Jar available via HTTP. Did you try uploading the jar/jad to the phone and "launching" it there. Nokia Application Manager which comes with Nokia PC Suite might be also a good choice.
You need to sign the application if you want to get rid of(to an extend) these kind permission issues. A signed application has more access to the device's resources such as camera ,network . Also the user can set the permission for the application ,such as "ask for first time", "ask every time ","Do not allow" etc... You will get more of these options if the application is signed .
To deploy you can use the software that Nokia has given ,the PC suit. or you can use the OTA method where you upload your signed( or unsigned) jar and jad files to a webserver and download the it from there using the mobile browser. Just open the jad file from your mobile browser, it will verify the certificate and will down load and install the jar file.
First method will be good enough till you are having the ready to go application.