RIMAPPSA2?

Similar Questions

• How to sign a library? RIMAPPSA2 unable to connect!

  Hello world

  I need to add a project as a library. But in the fist, I sign this library, and I can't sign this RIMAPPSA2!

  How to sign a libaryproject?

  Need HELP!

  Not really what I wanted. I wanted to say that RIM has some features and libraries that are not supposed to be avalible for the average developer.

  If you use these functions or library you get told you need a signature RIMAPPSA2 key (which you can not get).

  You need to try to find what is not public (or has been talked about on these forums that many people use). Then remove/replace them so you can sign your library.

• Signer of code RIMAPPSA2 unnecessarily required by the signing tool

  When I try to connect with the signature tool, it mentions RIMAPPSA2 as a required signatory. This thread

  http://supportforums.BlackBerry.com/Rim/Board/message?message.UID=20321 looks like RIMAPPSA2 is required for non-public API signing.

  The code that I'm building is however a self-contained generalist (no external dependencies) Java library 1.3 that does not have the BlackBerry platform and does not call any what BlackBerry non-public API (as the package from net.rim.vm. * mentioned in the post).

  In addition, the compiler doesn't even issue a warning that a signature is required, as it does for the duration RIM and BlackBerry Apps API.

  No idea why this requirement of signatory RIMAPPSA2 arrives unannounced here?

  Thanks for the suggestions!

  I realized what was the cause. It turns out that the problem is caused by a persistent native function declaration in one of the classes in the library I've been porting. Remove the native statements got rid of the requirement to sign RIMAPPSA2.

  Surprisingly, the compiler didn't warn at all the presence of the native declaration. I had pretty much remove entire packages and source files for the library construction bath until I put on the offending files.

  Thanks to the recommendations of RexDoug that I installed on the real device. That has proved to be a good idea. Although the cod file was missing a required signature, error messages that popped up when the application has been loaded were a bit informative.

• WebWorks and external cod

  Hi all

  I am trying to add a 3rd lib in my webworks app, but there is a problem. The pots contain .classes (stub methods, I think) and cod. I followed this guide and I've successfully compiled everything. However, after activating the signtool gui, I see that RIMAPPSA2 signatures are needed. I can install the application on my device, but then I get the error "cannot call native method.

  I was already able to encode a moped with these libs. They are properly signed by the seller. Environmental jde, I only need to add them to the path of building and then, after the signing of the output files, I simply add their COD through UpdateJad.

  No clue on how to solve it in webworks?

  THX

  Hello
  I'm not registered any missing key. Just adding my pots as shown in guide, seems to force the signtool to sign. So my solution is as follows: I removed the jars, but I left the tag dependency in the library.xml as shown (not sure if it's really necessary)
  I saw that bbwp basically reconditions everything and that what he calls the CAP. In the main folder webworks, I found a file named bbwp.properties. I added my pots in the import after the net_rim_api tag, using the ';' as the delimiter.
  After compiling, I used the updateJad tool to add cod of the 3rd party or external modules in my application.
  And it worked

• Cannot sign the library project

  I am a library project named Ksoap2 containing just the Ksoap2.jar for my main project and it works well on the Simulator, I can get the values of webservices. I try to deploy the project to a real device and test it, and an error is that ksoap2. COD must be signed, so I try to sign my projects. After you have installed 3 RIM csi files, I can sign my main project successfully, but not the library Ksoap2 project and I have this:

  File: Ksoap2.cod

  Status: Not registered

  Category: required

  SignerID: 3

  Name: RIMAPPSA2

  And then I tried with another jar for the library project, the results are the same, the status is not saved. Someone can help me, thank you very much!

  Third-party applications are not able to call regardess period, native methods if they are signed or not with signature keys.

  The native reference to the call should be deleted.

• BBM SDKS and code signing

  After plugging in version 1.1 of the SDK BBM on my application I wonder to sign code for what is called "RIMAPPSA2" in addition to the usual RRT, RBB, and CPR.

  So I guess my question is what I have to get an extra key from RIM or is there something wrong with the .jar file that I join?

  In case someone else runs into this, the solution is that not actually package you the SDK with the application. Instead, the .jar file is added to the project as a property (identical to the OS SDK). It is significantly different then how you would treat the PaymentSDK. Then do not include the .jar in the project you are is more invited to sign up for RIMAPPSA2.

• JDE 4.7 CAP question?

  I I have a problem with a JDE 4.7 code signing application and it seems that it is apparent to the CAP JDE 4.7 compiler.

  Basically I modified HelloWorld.java that comes with JDE 4.7 examples to add an API call control (see below for more details). Then, I compiled and generated the jad and jar files. After that, I used the following command line to generate the .cso, .csl and .cod files JDE 4.2 and 4.7 JDE environment respectively with exactly the same file jad and jar file:

  CAP import = net_rim_api.jar = HelloWorldSigning = HelloWorldSigning.jad HelloWorldSigning.jar jad codname

  However, I found that HelloWorldSigning.cso generated under 4.7 environment does not have entry "52525400 = RIM Runtime API" in it compared with that generated under environment 4.2. (The HelloWorldSigning.csl files are the same). As a result, the signed HelloWorldSigning.cod less 4.7 will get "attempts to access a secure API" error loading on devices of the storm, then the HelloWorldSigning.cod signed under 4.2 has no problem. If I manually fix the file cso by adding the missing entry under 4.7, it will solve the problem.

  No idea what's wrong with him?

  PS:

  HelloWorldSigning.csl under 4.2 and 4.7 as follows:

  52525400 = RIM API implementation

  HelloWorldSigning.cso less than 4.7:

  33000000 = RIMAPPSA2
  52424200 = RIM Blackberry Apps API
  52434300 = RIM API Crypto - Certicom
  52434900 = RIM Crypto API - internal
  52435200 = RIM API Crypto - RIM

  HelloWorldSigning.cso minus 4.2:

  3000000 = RIMAPPSA2
  52434300 = RIM API Crypto - Certicom
  52434900 = RIM Crypto API - internal
  52435200 = RIM API Crypto - RIM
  52525400 = RIM API implementation
  52424200 = RIM Blackberry Apps API

  Code source HelloWorld.java:
  /**
  *
  * HelloWorld.java
  * The sentinal sample!
  *
  * Copyright © 1998-2008 Research In Motion Ltd.
  *
  * Note: For simplicity, this sample application cannot operate
  * resource bundles and resource strings.  However, it is STRONGLY recommended
  * that make application developers use available location functions
  in the development platform BlackBerry to ensure uniform application
  * experience in a variety of languages and geographies.  For more information
  * on the location of your application, please refer to the BlackBerry Java Development
  * Environment Development Guide associated with this version.
  */

  package com.rim.samples.device.helloworlddemo;

  Import net.rim.device.api.notification.NotificationsConstants;
  Import net.rim.device.api.notification.NotificationsManager;
  Import net.rim.device.api.ui.UiApplication;
  Import net.rim.device.api.ui.container.MainScreen;
  Import net.rim.device.api.ui.Field;
  Import net.rim.device.api.ui.component.Dialog;
  Import net.rim.device.api.ui.component.LabelField;
  Import net.rim.device.api.ui.component.RichTextField;

  /*
  * BlackBerry applications that provide a user interface must extend
  * UiApplication.
  */
  class HelloWorldDemo extends UiApplication
  {
  /**
  * Entry point for application.
  */
  event object public final static = new Object() {}
  public String toString() {}
  return to "sing";
  }
  };
  Public Shared Sub main (String [] args)
  {
  Create a new instance of the application.
  NotificationsManager.registerSource (0x8f8c19257ffbb06fL, event, NotificationsConstants.CASUAL);
  PAP HelloWorldDemo = new HelloWorldDemo();
         
  To apply to enter the event thread and the beginning of message processing,
  We invoke the enterEventDispatcher() method.
  theApp.enterEventDispatcher ();
  }

  /**
  *

  The default constructor. All RIM user interface components creates and runs a push of the
  screen of the application root in the user interface stack.
  */
  HelloWorldDemo() private
  {
  Push the instance main screen user interface for rendering stack.
  pushScreen (new HelloWorldScreen());
  }
  }

  /**
  Create a new screen that covers the screen, which offers default standard
  * BlackBerry applications behavior.
  */
  / * package * final class HelloWorldScreen extends screen
  {

  /**
  * Manufacturer HelloWorldScreen.
  */
  HelloWorldScreen()
  {
  Add a field to the title area of the screen. We use a simple LabelField
  here. the SELECTION option truncates the text of the label with «...» "If the text
  It is too long for the space available.
  LabelField title = new LabelField ("Hello World Demo", LabelField.ELLIPSIS |) LabelField.USE_ALL_WIDTH);
  setTitle (title);

  Add a text field read-only (RichTextField) on the screen.  The RichTextField
  is active by default.  In this case, we provide a style to make the field
  non-focusable.
  Add (new RichTextField ("Hello World!", Field.NON_FOCUSABLE));
  }

  /**
  * Show a dialog box to the user with "Goodbye!" when the application
  * is closed.
  *
  * @see net.rim.device.api.ui.Screen #close)
  */
  public void close()
  {
  Display a farewell message before closing the application.
  Dialog.Alert ("Goodbye!");
  System.Exit (0);
         
  Super.Close ();
  }
  }

  Mark Merci for the quick reply.

  I have added the work around my build script, it seems to works fine.

• Signature accelerometer keys not enrolled?

  Hello

  I'm trying to sign the accelerometer with JDE 4.7.0.35 demo (and tried by Eclipse as well, although I'm sure they use the same signature tool). When I go to Build-> ask for Signatures, the Signature tool tells me that what follows is not registered:

  File: AccelerometerDemo.cod

  Status: Not registered

  Category: required

  SignerID: 3

  Name: RIMAPPSA2

  I have no other keys (RBB, CPR,...) and I signed requests before. Just having a hard time to sign this demo of the accelerometer. In the end, I am signing a request that will be using the accelerometer data, but since that didn't work, I decided to try to sign the demo and I met the same problem.

  I'm doing something wrong / odd here? I'm not new to BB development and it is a problem that I saw when I tried access protected EDGE API. But I do not understand why the API calls in a demo application would bring this issue.

  Any help/assistance on this issue would be greatly appreciated.

  Thank you.

  --

  Mahan H.

  3 key signature should not be required for the accelerometerdemo.  There was a problem in a beta of version 4.7.0 BlackBerry JDE that have marked this demo requires a signature 3 keys.  Please upgrade to the gold version of the BlackBerry JDE 4.7.0 version found here: http://na.blackberry.com/eng/developers/javaappdev/devtools.jsp

• Error checking 2745

  When I introduced the code for BlackBerryCanvas and TouchEvent at my request, I started having some error checking 2745. I suspect this is related to my application signature. If Yes, what is the ID of the required signatory, so I can add to my cso file?

  Current content of CSO:

  33000000 = RIMAPPSA2
  52424200 = RIM Blackberry Apps API
  52434300 = RIM API Crypto - Certicom
  52434900 = RIM Crypto API - internal
  52435200 = RIM API Crypto - RIM
  52525400 = RIM API implementation

  Thank you.

  Ah. It turns out that my build script mentioned the JDE 4.5 for the CAP. Thank you.