Trial bar signed on simultor

I just signed a bar file and I want to test Simulator.

How can I do?

BlackBerry-airpackager-installApp-device - Word password

or just type blackberry-airpackeger in your windows command line tool to get more information

Tags: BlackBerry Developers

Similar Questions

  • File bar SIGN IN to BB 10 of eclipse Android App

    Hello I tried to sign the files bar so I did it after step

    First Windows - > Preferences - > Blackberry - > Blackberry SDK tools - > Bar signatory

    I have certified applications

    and then

    Right click on the android project - > tools-> SignIn for APP world Blackberry

    Now you can see the bar file is generated without error will be looking like below

    but when I do this bar file zip and try to download blackberry app world I m getting error like this

    can anyone suggest me how to solve this error, because I have already signed with the certificate, but still I get the error message

    "Bar is not signed RDK bar isn't signed AUTHOR this bar contains unsinged entries who have nto.

    Try to use the signing of the app on the web

  • Subscription shows trial after signing out and back in CC

    My subscription is always also a trial with 28 days left after the purchase.   I signed in and out of the CC from many times and there is no change.   Does anyone know what I can do to fix this?

    Please visit: Creative Cloud applications unexpectedly back in the test mode. CS6, CCM

  • Signing keys for different from Android NDK bar signing keys?

    I've already implemented the dev environment and I signed and sold since Android apps and games.

    Just downloaded NDK and I was wondering what I need to ask another key of song to sign NDK apps or the same keys will work?

    No, you don't need new keys.  The same code signing keys can be used in all the PlayBook and BlackBerry 10 SDKs.

  • Paid for flash, still on trial after sign in.

    I paid for a subscription to the month, and he always acts as if UI does not. Strangely, the days of hearing are reset to 30, or sometimes it reads, 'You can try this product for the days' 32767 Any help?

    See if the following can help:

    Creative cloud returns to the Mode of assessment
    ------------------------------------

    http://helpx.Adobe.com/Creative-Suite/KB/trial--1-launch.html

  • I bought plan photographer but Lightroom has always limited functionality and 'Trial expir├⌐' sign in CC.

    Departure

    Check in the pictures folder. [you can locate all catalogues. ]

    Try to manually load the old catalog.

  • The bar is not signed AUTHOR

    Hello

    I'm manually signing my 10.1 SDK bar file built using the following which returns "Bar signed" by pressing.

    'C:\bbndk\host_10_2_0_15\win32\x86\usr\bin\blackberry-signer' bbidtoken - Mybbidtoken.csk - storepass $MYPASS$ MyApp - 1_0_0_5.bar RDK

    However when I try and publish it for Blackberry world, I get the following error on upload.

    "Bar is not signed AUTHOR."

    Thank you

    Hi Mark,

    Sorry, that was my mistake, I forgot to remove the option RDK the second bat file that I had created for provider 'B' now that I have it removed I am not getting any error...

    Thanks a lot for your great, dedicated and great support...

  • Cannot install the signed file BAR, [if the argument "blackberry - sign - sigfile ' is not GPACACF]

    Hi all

    I have following queries on the use of certificates in BAR files.  Certificates are defined by the user.  [ie. certificates created locally using this link 'http://developer.blackberry.com/native/documentation/core/com.qnx.doc.nfc/topic/manual/t_nfcdevguide...

    Queries are

    1. the '-sigfile "command argument"blackberry-signer", if I have any other purpose than"GPACACF", I get the error message following ' result::failure 880/var/tmp/cgic851170: cannot access the Member ' META-INF/FILEACF.» EC'

     

       2 can I sign several certificates [one after the other] using the command "blackberry-signatory"?

    Forward to your response

    OK, I tested the procedure in the documentation and created a file of key PKCS #12 and gave my key an aliass MYALIAS. See the details here:

    $ openssl pkcs12 -in selfsign.p12 -info
    Enter Import Password:
    MAC Iteration 2048
    MAC verified OK
    PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2048
    Certificate bag
    Bag Attributes
        friendlyName: MYALIAS
        localKeyID: D8 CB 15 E1 B3 30 0C 90 C0 57 EB FA A1 D4 20 BB 1C EF A7 40
    subject=/C=GB/ST=Berkshire/L=Slough/O=BlackBerry/OU=DevReel/CN=Test/[email protected]
    issuer=/C=GB/ST=Berkshire/L=Slough/O=BlackBerry/OU=DevReel/CN=Test/[email protected]
    -----BEGIN CERTIFICATE-----
    MIICgTCCAeoCCQDgvIXlO1lIYDANBgkqhkiG9w0BAQUFADCBhDELMAkGA1UEBhMC
    R0IxEjAQBgNVBAgMCUJlcmtzaGlyZTEPMA0GA1UEBwwGU2xvdWdoMRMwEQYDVQQK
    DApCbGFja0JlcnJ5MRAwDgYDVQQLDAdEZXZSZWVsMQ0wCwYDVQQDDARUZXN0MRow
    GAYJKoZIhvcNAQkBFgtmb29AYmFyLmNvbTAeFw0xMzA4MTYxMTQ0MjFaFw0xNDA4
    MTYxMTQ0MjFaMIGEMQswCQYDVQQGEwJHQjESMBAGA1UECAwJQmVya3NoaXJlMQ8w
    DQYDVQQHDAZTbG91Z2gxEzARBgNVBAoMCkJsYWNrQmVycnkxEDAOBgNVBAsMB0Rl
    dlJlZWwxDTALBgNVBAMMBFRlc3QxGjAYBgkqhkiG9w0BCQEWC2Zvb0BiYXIuY29t
    MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDskC5uCv6eGgZvrXpWJsXz11HK
    POCraWH7QfWEaa/d82SusTVVL2UEqcWhRKHGD3ogikyQ+p4MiCKViYKXG2067nfv
    C+yNUupinb7Bsx/YsUp5zv135fpMXn9rSD/P5LegQONxVqeW5ZoSc3br4JAmYoFq
    uwnNQJl+0AeD7HUjUQIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAKSKibcQgvho0kPU
    E53TWjiVTOxxMzpu2F3/y1McEeOwg0bvTvfoGm3fFJnVM/B1509QgEVenSuO4Am8
    CrF9MCdRA8HJeAw2P7YHSwRgc9nn1HqkqF1McRi+DVCwIfWUFCyD9Wllb5PWPlkD
    voqNLCtuuYRyoIGq+gANBXLOlg1m
    -----END CERTIFICATE-----
    PKCS7 Data
    Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048
    Bag Attributes
        friendlyName: MYALIAS
        localKeyID: D8 CB 15 E1 B3 30 0C 90 C0 57 EB FA A1 D4 20 BB 1C EF A7 40
    Key Attributes: 
    

    I then used blackberry - sign to sign a file bar:

    >> blackberry-signer -keystore selfsign.p12 -sigfile GPACACF -sigalg SHA512withRSA -storepass barfoo -verbose NfcChicken-1_0_0_20.bar MYALIAS
    SF Digest =
    4e 0e 9c 25 a5 2e 0a 1a b9 c0 d2 f8 7c 9e 05 e1
    65 39 eb 92 4e 1d db d8 9d 11 f5 8f 84 b0 92 75
    48 3e 53 40 b6 e3 b9 cc bd 6e 7e 61 95 7b ba d5
    6e b1 76 be b6 c5 d9 a7 ac f3 ad c0 1f fd e7 8a
     Updating: META-INF/MANIFEST.MF
       Adding: META-INF/GPACACF.SF
       Adding: META-INF/GPACACF.RSA
      Signing: native/bar-descriptor.xml
      Signing: native/icon.png
      Signing: native/assets/images/brown_egg.png
      Signing: native/assets/images/Thumbs.db
      Signing: native/assets/main.qml
      Signing: native/assets/sounds/chicken1.wav
      Signing: native/qm/NfcChicken.qm
      Signing: native/NfcChicken.so
      Signing: native/assets/.assets.index
    Info: Bar signed.
    

    If you look at the signed file bar, you can see the GPACACF. SF and. RSA files in the manifesto bar.

    If I use the following command

    >>blackberry-signer -keystore selfsign.p12 -sigfile XYZ -sigalg SHA512withRSA
    -storepass barfoo -verbose NfcChicken-1_0_0_20.bar MYALIAS
    SF Digest =
    4e 0e 9c 25 a5 2e 0a 1a b9 c0 d2 f8 7c 9e 05 e1
    65 39 eb 92 4e 1d db d8 9d 11 f5 8f 84 b0 92 75
    48 3e 53 40 b6 e3 b9 cc bd 6e 7e 61 95 7b ba d5
    6e b1 76 be b6 c5 d9 a7 ac f3 ad c0 1f fd e7 8a
     Updating: META-INF/MANIFEST.MF
       Adding: META-INF/XYZ.SF
       Adding: META-INF/XYZ.RSA
      Signing: native/bar-descriptor.xml
      Signing: native/icon.png
      Signing: native/assets/images/brown_egg.png
      Signing: native/assets/images/Thumbs.db
      Signing: native/assets/main.qml
      Signing: native/assets/sounds/chicken1.wav
      Signing: native/qm/NfcChicken.qm
      Signing: native/NfcChicken.so
      Signing: native/assets/.assets.index
    Info: Bar signed.
    

    using a sigfile - XYZ to sign the file bar and the bar file contains:

    showing the XYZ. SF and. RSA files added to the clear bar.

    I don't see the error that you notice.

    The documentation notes that this form of blackberry-signer syntax is available only on recent versions of th emost of this command. I ran these commands on the current beta version 10.2 public but it should work with 10.1.

    What version of the SDK yuou use?

  • Conversion of the apk from bar on jenkins build server

    Hello

    I somehow got in trouble to try to configure the server to build jenkins to convert my apk to bar. I use this script for the conversion that works very well

    #!/bin/sh
    
    cd /var/lib/blackberry.tools.SDK/bin
    ./apk2bar ../apk/ /var/lib/android-sdk-linux -t /var/lib/blackberry.tools.SDK/barRelease -a ====PRIVATE=== -cm
    

    But what Truing package bar sign, author.p12, barsigner.csk barsigner.db client-RDK - xxxxxx.csj are

    /var/lib/blackberry.tools.SDK/
    
    #!/bin/sh
    
    cd /var/lib/blackberry.tools.SDK/bin
    ./batchbar-signer ../barRelease /var/lib/blackberry.tools.SDK/author.p12 $PWD $PWD
    

    I get only

    Error: Certificate chain not found for: RDK.  RDK must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.
    

    Building is not under windows with toos command-line or GUI with the same key works fine, but under jenkins. What is the problem?

    Fixed.

  • Packaging and signing in Flash Builder Burrito using 0.9.4 SDK

    Hey guys. I know frankly, there are 1 million post on the forums about this, but I wanted to be sure and had a few questions myself. Good so I used Flash Builder Burrito to sign and package my request. My app is a Mobile Flex Application and I use 0.9.4 SDK. I used the MANY post on this forum through signature and methods of packaging and it worked perfectly, no errors at all. The two files that I got after conditioning and signature was my apps .bar and bar.sign files. I saw in other post to extract the .bar file to see if its signed and if the icon is there. How do you do this will WinRAR or PowerISO to extract this file type. I fear only because all Iv seen post are all saying theres tons of bugs with the packaging and signing using burrito, but all I could see was that they were using the SDK 0.9.3. Should I have a problem with my .bar file? I don't know how to extract my .bar file to view the contents, so I can at least check to make sure that it is signed and packaged properly. Can someone me another message or an article on how to extract the .bar file and check to make sure that its all good to present, RIMM. My previous version was rejected of RIMM is not signed and sent the Bug of version. I have just re-climbed the .bar I got to use the new SDK and had no errors, so I hope this is right. Anyway thanks in advance and any help would be great.

    The .bar file is just a zip file.  It will work any util that allows to read a zip file.  If you need to rename the .bar to a zip file, which is OK, but be sure to rename it before upload.

  • How to change Qt creator to build without - devmode - bar debugtoken?

    I'm trying to deploy Qt applications that I have updated to work with the last update of OS as well as the creator of Qt bb published here: https://github.com/blackberry/Qt/downloads

    I run the installation of linux.

    The release/debug switch does not work to remove the devmode-blackberry-nativepackager call debugtoken.

    So I thought no problem, I'll build and sign the order, here are the issues I have with that.

    First of all, Packager complained the matter in the descriptor indicating that % QT_INSTALL_IMPORTS % is an invalid path. Then I put in the required absolute paths and managed to build the package bar.

    Bar-signer will not sign the package, well complain:

    Error: Code signing request failed because [run_native] in Entry-Point-User-Actions is not allowed.
    

    So I remed out: run_native starting from the descriptor, still no joy, it will fail with the same message...

    Does anyone have any idea how to change the call to blackberry-nativepackage of the creator? Or any other tips as to where I'm wrong here?

    I could be missing something obvious here in my frustration!

    Thank you

    Jon

    I * think * this message is what you get if you have a run_native, without the system = 'true' part. If I'm right, he can point to that you have a duplicated elsewhere with the wrong content descriptor file, and it's using this rather than the one you are changing. Or something like that.

    To resolve these issues, always go to the MANIFEST. MF file in the actual .bar file. Unpack and inspect this file directly to see what it is * really * for help. Often, you can identify a gap like that and then trace back to repair your build system.

    Oh, and I must be close to correct that since, if you really had system = true, that entry would have shown upward in Entry-Point-system-action at the place where the error says it's. (Unless the error itself is completely wrong).

  • Package id error. Signed applications WebWorks.

    Could someone please tell me why when signing of the same app for OS BB10 and PlayBook OS I'm different application id in MANIFEST. File MF, which translates as the rejection by the supplier portal .bar file downloading.

    Two software development kits are recent, if it's important.

    Unchanged demand, has signed for various devices.

    The two signature process managed just different Package name in the MANIFEST. MF file. (Must be the same because same config.xml served.)

    Keys used are the same.

    Here are some examples:

    BB10 MANIFESTO. MF

    Package-Type: application
    The package author: me - it's always the same with key set
    Package name: XXX - specified in the xml file must be the same
    Package Version: 1.0.0.0
    Package-Architecture: armle-v7
    Package-author-certificate-Hash: xxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxx
    Package-author-Id: me - it's always the same with key set
    Package-Id: this should be the same for both packages since the Package name is the same
    Package-Version-Id: number of Version loads
    Package - Issue Date: 2013-04 - 28 T 08: 18:12Z

    PlayBook MANIFESTO. MF

    Package-Type: application
    The package author: me
    Package name: XXX608d35518356ae28ab6cb8e8ck6b11b - see what screws everything up
    Package version: 1.0.0.5
    Package-Architecture: armle-v7
    Package-author-certificate-Hash: xxxxxxxxxxxxxxxx xxxxxxxxxxx
    Package-author-Id: me
    Package-Id: not the same thing because of the different package name
    Package-Version-Id: number of Version loads
    Package - Issue Date: 2013-04 - 28 T 08: 18:18Z

    608d35518356ae28ab6cb8e8ck6b11b - this is what's wrong with the name of the Package.

    .bar signed for BB10 comes with Package name normal one specified in the config.xml file in the identification sticker. .bar signed for PlayBook OS comes with the package name that resembles what would like normal more lots of numbers uttachet him he looks a bit like a hash keyword. But there simply just to imitate what is specified in the tag of the config.xml file.

    As I said package PlayBook is rejected by portal provider for some reason "different ID of Package". (Why Package ID would be the same if your own BlackBerry signature tools mess). BB10 verson was transferred first. What I'm trying to tell if verson PlayBook would be first, then the BB10 version would be rejected for exactly the same reason.

    That leaves me with two options:

    1. try to solve this problem with the support of the seller. (Not going, the last time I'm angry "why did you change your package of them ID")

    2 forget PlayBook, at least with OS its market now. (Who cares anyway, upload was almost merciful because it is not worth even the whirlpool to go thrugh signature and the download process, which is particularly hideous for PlayBook).

    The third option would be just to create something like 'Application for PlayBook' in portal provider, but that's all just stupid because it would be the same application but under different names therefore not cross-platform for users of BlackBerry ID.

    Also can't help but to say rim (BlackBerry) should gather their things and come up with a single tool can be used to sign applications. Because they have now looks more like a joke if it isn't insult all together. Process is mindbending. and if you want yourself (almost 100% certainty) frustrate develop, sign and app World de BlackBerry download. You will be pleased.

    Anyway everyone has had similar problem when downloading the BB10 and PlayBook .bars to the provider portal would be nice here how solve you it.

    See you soon! And the development of the happy. (which isn't the most difficult part, but you already know)

    This is because that the WebWorks SDK for Tablet added a random GUID to the package ID to make it unique.  The BlackBerry 10 SDK is no longer for it.  Unfortunately, this means that if a developer rebuilt their code even using the SDK for the new platform, then BlackBerry World will not see them as being of the same application (since the internal ID is different).

    There is a solution - what you need to do is change the id property of your element in the config.xml file to match the package-name of the file 'manifest '. MF' Tablet-OS.

    Here is an example of what I mean.  If the MANIFESTO of the PlayBook. MF file shows that 608d35518356ae28ab6cb8e8ck6b11b has been added in the name of the package of fooBar, then set your id like that

    http://www.w3.org/ns/widgets"
            xmlns:rim="http://www.blackberry.com/ns/widgets"
            version="1.0.1"
            id="foobar608d35518356ae28ab6cb8e8ck6b11b"
            xml:lang="en">
    

    It's not pretty, but it works.

    Once you recompile, BlackBerry World will then recognize the bar and allow you to present a new bundle for the existing version.

  • Create the certificate and Code signing

    Hi all

    I'm still a little confused on the operation of the certificate and the sign Code.

    First I used Flash Builder Burrito to create my certificate and I choose my file syc. After that, I got an email from RIM saying that my registration has been completed. After that, I realized that the certificate I created has a different name than I used to ask my sign code. When I created a new graduate with the right name, I could associate the core sign in my new certificate and get this error

    When I tried to sign my application via command line, I've got it successfully: "Bar signed."

    Does anyone know why I get this error message, and if the command line worked really. can I use different certificate with a sign code?

    Thank you very much

    Hey arthur,.

    the rule is that if you mess up the record in some way, it is best to ask a new set of signature keys. You can not reinstated a key already registered. also, I saw that you use Flash Builder to make the entry to the registry. Although I've seen this work, I recommend that do the actual packing and signature via command line. Good luck!

  • How to test your subject bar file

    Hey guys,.

    Yesterday, I presented my first app tablet with some difficulty. Firstly, I was not able to compile my code with the SDK 0.9.3 because it supports more "mobile applications", which is how my application was created. I then created my signed the key, but when it came time to package the application with the keys I have been unable to do with the command-line finally as a last resort before calling it a night I decided I would try package and sign my application through Flash Builder Burrito. It seems to work a bar and a bar.sign file has been created and no error is thrown.  I decided to create a zip of those and submit it for review.

    Today, I'm worried that my application might get rejected because it lacks an icon, there is not sign or he does not get properly packed by flex builder. So my question is possible for a) confirm that the app is sign? and (b) test of the bar folder with the Simulator.

    Thanks in advance for you help!

    Hey,.

    Welcome to the forums! If you have indeed the procedure of signing through the Flash Builder / Burrito app, there is a good chance she has no more. The process in Burrito is very misleading because it throws any errors that you may encounter. The signing and packaging must be made through command line. At the moment there is no other way. If you run problems, post on the forums and maybe we can help you with all of the errors. Good luck!

    Edit: here are some additional forum messages that may help shed more light on the question:

    Bug in Flash Builder - why the command line is required:

    http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/howto-sign-your-applications-from...

    How to check the content of your signed and this bar you can find inside:

    http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/howto-sign-your-applications-from...

    My discussion with the rundown of how to sign an application (many others available around forums):

    http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/useful-tip-package-images-via-com...

  • I plugged my USB Modem to the computer, it's MMX352G micromax modem. After you connect to the internet, all browsers open the pages of the BM, but in the taskbar sign of the network is to have a red cross. Why?

    I plugged my USB Modem to the computer, it's MMX352G micromax modem. After the internet connection all browsers open the pages of the World Bank, but in the task bar sign network is to have a Red Cross and when I go over it, it says not connected, but I can always use internet in my browsers. Why? It causes an adverse effect on my computer.

    Hi Akash,

    Welcome to the Microsoft community. According to the description of the bar icon problem tasks of the network have a red x, but you can still access the internet. Provide the following information:

    ·         Did you do changes on the computer before the show?

    ·         You use a third-party security software?

    I suggest you follow these methods.

    Method 1: Follow these steps:

    Step 1: Start the computer in safe mode with network and check if the problem persists.

    Startup options (including safe mode)

    Step 2: If the problem does not persist in safe mode with networking, perform a clean boot to see if there is a software conflict as the clean boot helps eliminate software conflicts.

    Note: After completing the steps in the clean boot troubleshooting, follow step 3 from the link to start the computer to a Normal startupmode.

    Method 2: Follow the steps in the article.

    Windows wireless and wired network connection problems

    You can read this article for more information:

    How can I troubleshoot network card?

    I hope this helps. Let us know if you need more assistance.

Maybe you are looking for