Bar-descriptor versionLabel

Similar Questions

• How the packet data / * ($HOME /) files by using the bar - descriptor.xml

  Hi, using sdk native c / c ++ with playbook Simulator 1.0

  I want to distribute with my application some data files that likely should fall under the ' data /' ($HOME?)

  folder.

  (I've written / will update them sometimes, so app/native/does not appropriate I suppose.)

  in the bar - descriptor.xml, I tried adding them as an 'active '.

  who drops their bottom right in app/native / *.

  so I change the XML .bar to try to get them grounded in data.

  Here's what I found:

  by train: data/filename landed the file in app/native/data/filename

  try:... /... / Data/filename received the error

  by train: / data/filename received the error (hoping to slash leader was compared to the sandbox)

  I even on a lark tried: $HOME/filename, who literally created file app/native / $HOME!

  so he tried a ${HOME} with the curlies. I got an error saying unable to resolve the path variable.

  How can I get the data files in the folder/data ($HOME) using the .bar packaging?

  You cannot package the file into the data, you copy your files at startup, if they don't not exist your app/native/data for example

• bar-descriptor for Blackberry 10.3 warnings

  I get under warnings for my bar-descriptor but according to article blackberry, all these permissions are valid for blackberry 10.3. I don't know what is the problem here. Keep it raise warning when I try to export release builds. can someone help me undestand this?

  '_sys_headless_nonstop, system' is not a valid authorization for the 10.3.0 API level

  'read_phonecall_details' is not a valid authorization for the 10.3.0 API level

  'acceses_pimdomain_calllogs' is not a valid authorization for the 10.3.0 API level

  http://developer.BlackBerry.com/native/documentation/Cascades/dev/tools/app_permissions.html

  The warnings are deleted if you generate using the SDK 10.3.1, but they should not cause an error.  Code snippets that you reported looks good, but there is probably a problem where you have placed the lines permission.  Compare where you placed the sample headlessservice.

• Retrieves the version number of bar - descriptor.xml programmatically

  Is there a way to extract a version number, and other information of bar - descriptor.xml file similar to how's done it in the Android world via getPackageInfo() in PackageManager?

  It would be a convenient way to play around these values in your code.

  Thank you

  There are various APIs of the platform that you can use for example the PackageInfo

  http://developer.BlackBerry.com/Cascades/reference/bb__packageinfo.html

  ApplicationInfo or,

  http://developer.BlackBerry.com/Cascades/reference/bb__applicationinfo.html

• The file of the bar - descriptor.xml (and make the application of command line)

  I made a game with air and it is online for sale on Android and iOS. It is somewhat popular and I thought to put up on Blackberry for quite awhile now and with the Port of soon-to-start-A-Thon, this seems to be a great time to finally make it.

  BlackBerry is not very common that here where I live in Sweden, however it still looks like an interesting with a potential platform if I want to get the trip. Unfortunately I don't own a camera myself so I'll use the Simulator. With some graphic problems with the simulator when running in mode BB10DevAlpha (icons does not appear right) and the Simulator is very slow when running in mode BB10DevAlphaSafe (chart appears on the right, but it seems that updating them requires more CPU my computer are available).

  The game is built using nothing other than Adobe Flash Professional CS6 and a bunch of command line tools to build the package and sign. I've only got an old computer with Windows XP now since the death of my main PC, all at the time and since the Port-A-Thon is just a few days I do with what I got.

  Firstly I understand that only AIR 3.1 is supported by Blackberry 10, so I use the old AIR SDK 3.1 to create a SWF (flash) file.

  What I really need to do should be used in the exported SWF file of the game, then use the command line tools provided by RIM to build the package, right?

  Except that I did not count on bar - descriptor.xml to be so difficult to understand.

  I was brought to the documentation here: https://developer.blackberry.com/air/documentation/bb10/bar-descriptor_config_file.html

  It says Adobe AIR at the top, the platform selected is Blackberry 10 and the title says "bar-descriptor configuration file", so it must be in the right place!

  I start by trying the 'bar-descriptor configuration example file"on this page:

  ===========================================================

  
  
    
        None
        fake
    
   
    
     Name of the author
   
    
     gXXXxXXx ##XxXxXxxxXxXX #xxx
   
    
     Core.Games
   
    
     Icon.PNG
   
    
     HelloWorld - splash.png
   
    
     read_geolocation
     use_camera
   
    
     1
  

  ===========================================================

  Of course during the test I replaced a few things in the example above with the correct filenames for images etc, I just copied the example of right - off this time to you guys show what I mean.

  Firstly, I extract "blackberry-tablets-sdk - 3.0.0" in a folder on the disc, then I make sure as a full path to the "bin" in the SDK folder inside the path on the OS environment variable.

  Then I read on "Applications of Test using the command line": https://developer.blackberry.com/air/documentation/bb10/testing_your_application_cmd_ms_2010851_11.h...

  Now I run:

  BlackBerry - airpackager.bat - package installApp - blackberry-myappname - new.bar - launchApp myappname-blackberry-bar - descriptor.xml myappname.swf myappnameicon86.png bg splashscreen1024.png - device 192.168.8.128

  Note that "bg" is a folder with 500 images that must be accessible from the app. I hope that I can just add the folder like this and not type a path to each image file...

  What I get (in lib\adt.jar via the bat file):

  error 101: Namespace is missing
  Error: Validation of the AIR is not

  Okay, so the example did not straight on the box.

  Now, I've read all paragraphs in the first URL I linked above ("the bar-descriptor configuration file"). I start my own XML file and make sure to include everything that is marked as "necessary". That's what I'm left with:

  ===========================================================

  
  
      MyCompany
      
          
          com.mydomain.myappname
          My App name
          3.0.0
          
              splashscreen1024.PNG
          
          1.5.0
      
      run_native
      
          application
          
              bb.action.VIEW
              application/octet-stream
          
      
  

  ===========================================================

  I have no idea of what concerns the block whole call target, but it took, so he must be there.

  Now I launch (notice that myappnameicon86.png is gone since no icon is mentioned in the above XML code, it is not mandatory):

  BlackBerry - airpackager.bat - package installApp - blackberry-myappname - new.bar - launchApp myappname-blackberry-bar - descriptor.xml myappname.swf bg splashscreen1024.png - device 192.168.8.128

  Yet once, I get:

  error 101: Namespace is missing
  Error: Validation of the AIR is not

  Frustrated I get autour on the forums for answers, because the official documentation is nowhere getting me.

  I'm left with this:

  ===========================================================

  
  http://ns.Adobe.com/air/application/3.1">
      com.mydomain.myappname
      1.5.0
      
      My App name
      
      My App name
      
      
          myappname.swf
          standard
          fake
          true
          true
          landscape
          GPU
          fake
      
      
          myappnameicon36.PNG
          myappnameicon48.PNG
          myappnameicon72.PNG
      
      fake
      fake
      
          qnx.fuse.ui.skins.QNXDevice
          qnx.fuse.ui.skins.QNXNetwork
          qnx.fuse.ui.skins.QNXSensors
          qnx.fuse.ui.skins.QNXSkins
      
  

  ===========================================================

  Looks like the XML code that I use when I build for Android.

  First of all it doesn't have the tag root of qnx, but also nothing of the icons are of the required size (86 x 86). The tag required splashscreens and invoke target is also absent, to name a few. No idea of what the entire block of 'extensions' really do.

  Surely, this does not work:

  BlackBerry - airpackager.bat - package installApp - blackberry-myappname - new.bar - launchApp myappname-blackberry-bar - descriptor.xml myappname.swf QNXDevice.ane QNXNetwork.ane QNXSensors.ane QNXSkins.ane myappnameicon36.png myappnameicon48.png myappnameicon72.png bg-device 192.168.8.128

  Success in building the package BAR to my infinite surprise!

  He even managed to install on the Simulator. An icon for the game. However when it auto-couru the app went into landscape, thought for a second and then crashed (or you leave?) without a message.

  Perhaps because the required qnx tag was missing in the XML?
  Perhaps because images in the bg file could not be loaded?
  Perhaps because he had no permission to keep screen from dimming?

  I have no idea. I tried to add XML to qnx at the address previous to the bar - descriptor.xml, I thought that maybe he needed both the qnx block for when you run the application and the application block for when packaging. But now, he has complained of something like XML is not not clean ("' fatal error: markup in the document following the root element must be well-formed." ").

  So he came to it, I have to ask for help if I ever make the deadline of the Port-A-Thon.

  (1) how am I supposed to write the bar - descriptor.xml?
  (2) what command line starting by "blackberry - airpackager.bat" is OK to use?
  (3) all I have to do is build the SWF using Adobe Flash Professional CS6 and then pack it using the Blackberry SDK, right?

  First of all, there are two xml files that you need.

  One is called the manifesto, is to AIR and is called yourappname- app.xml. It is identical to the ones you use for Android and IOS, though some elements will be ignored. It's one you need to switch on the command line, and is probably causing the 'Namespace' missing error message. A file manifest a minimum is:

  
  http://ns.adobe.com/air/application/3.1">
  
      com.example.appname
      My Fabulous Game
      1.0.0
  
      FileNameOfYourSwfWithoutExtension
      YourCompanyName
      
          [This value will be overwritten by Flash Builder in the output app.xml]
          true
          false
          none
          cpu
          false
      
  
  

  Replace the text in red with your own stuff.

  The second xml file is called to the bar of descriptor. It is for App World and the installation process and is called bar - descriptor.xml. It contains information about signing code, icon, permissions etc. A simple bar - descriptor.xml is:

  
  
     
        none
        true
        landscape
        false
        cpu
     
  
     
     your-name-on-certificate
     your-id-on-certificate
  
     core.games
  
     
     1
  
     
     
        icon86x86.png
     
     splash-landscape.png
  
     
     2.1.0.1314
  
     
     access_shared
     access_internet
     play_audio
     set_audio_volume
  
  

  Make sure that you at least change the red dots.

• bar - descriptor.xml: which category for app use?

  Hi @all,

  I'm developing an application of battery. In the file of the bar - descriptor.xml I choose as single category 'media' and 'games '. Do I have to select 'Media' or let him no classified?

  Thank you very much!

  Peter

  I don't think it's really important, but I would not leave classified

• Disable the file of the bar - descriptor.xml automatically update

  Hello

  My application is dependent on an engine.so file.  the bar - decripptor.xml contains the following lines:

  
  armle-v7
  MyTest
  lib/libengine.so.1

  The problem is, when I clean and engine rebuilding in the IDE, the following line will automatically be removed from the .xml file. How do I disable this feature?

  lib/libengine.so.1

  Try turning off the generator called validator descriptor bar (right click-> properties-> Builder project)
  Make sure the library is there, then close the bar descriptor Editor
  So don't rebuild you.

• What is the file *.so in bar - descriptor.xml

  Hello

  in the bar - descriptor.xml to assets, that I find under build paths of target configurations for the debugging of the device, the device profile etc. For the configuration of the path the target name of the application, for example, in the notebook-app the target path is portable.

  Only for the configration of device-release, it is notebook.so.

  Can some explain to me why there is the suffix .so?

  I searched the web but can't find an explanation to this day.

  .so is a library.

  For a Release version that the main application is packaged as a library, it has been introduced with 10.1 (?) and gave a performance gain important that all qt libraries are compiled into a single.

• Access to the bar - descriptor.xml within the app

  Is it possible to get the properties of the bar - descriptor.xml? Particularly interested in the app id to understand app whenever it is a free or paid application version

  There are PackageInfo and ApplicationInfo classes that contain this information:

  http://developer.BlackBerry.com/Cascades/reference/bb__packageinfo.html

  http://developer.BlackBerry.com/Cascades/reference/bb__applicationinfo.html

  To extract the appId:

  #include ...
  
  bb::PackageInfo pi;
  QString appId = pi.name();
  

  Add LIBS +=-lbb in the .pro file

  You can also analyze the file manually, these threads contain more information on how to locate it:

  http://supportforums.BlackBerry.com/T5/native-development/extract-version-number-from-bar-descriptor...

  http://supportforums.BlackBerry.com/T5/native-development/APIs-to-access-bar-descriptor-XML/m-p/1737...

• bar - descriptor.xml abnormal when it opens

  Hi all

  When I open the bar - descriptor.xml, it just show the contents of the xml file.

  It should display the sections 'Problems' and 'Actions and related settings. But now it shows just the following content:

  
  
  http://www.QNX.com/schemas/application/1.0">

  Does anyone know how to solve?

  Thank you.

  brad_qqq

  @DrShavargo-Thanks for your help. And I find the solution.

  Has tabs at the bottom of the window opening of bar - descriptor.xml, there. :

  General, Application, assets, location and Source.See the pic below:

  

• How to check the authorization of app that is declared in the file of the bar - descriptor.xml

  How can I check the programitcally app permission is enabled or disabled.

  Suppose the first when we launch the application that any permission has been activated once the user has disabled permissions from the setting. So, I need to check the permissions are enabled and disabled.

  Thank you.

  access_shared , you can check with QFileInfo

  QFileInfo info("shared/documents");
  if (info.isWritable()){
      qDebug() << "SHARED PERMISSION OK";
  }else{
      qDebug() << "SHARED PERMISSION ERROR";
  }
  

  and the access_internet hm, if you do not have permission to access_internet in your application, then app still has access to internet, so that you can not check. You check only if app is connected to the internet

• BES10: Entry-Point-Name in the file descriptor META-INF/MANIFEST. MF is not valid

  Hello

  We have a Headless, built using 10.3 SDK Blackberry app. It has two parts. User interface and service without a head. We are able to package, sign (using the certificate of the company) and test it on BB 10 devices. Up to now, we use chrome extension 10 BB playbook/App manager to install the application on the device, but today when I tried to publish the App via our system's internal BES10 I get following error.

  • The "Entry-Point-Name" attribute with the value 'Background to the ExampleApplication Service' in the file descriptor META-INF/MANIFEST. MF is not valid.

  It seems that BES10 Server loved point of entry for background service but don't know why? It works fine when download us it via the chrome extension 10 BB playbook/App manager. Attaching sanitize bar - descriptor.xml for reference.

  Yes, it seems that there are limitations on the maximum length of the name of the application when published by BES (25 characters). Strangely affecting 'Point-name entry' to less then 25 characters solves the problem.

• App installs on Z10 when the icon & Splash Screen images are added to the handle Bar

  HI - don't know if it's an unusual question, but my app not install/load on my Z10 when one or both of the pictures icon and Splash Screen are added in the descriptor of Bar.  I development mode and have an installed debugging token and it is still valid.  The strange thing is that the application will be installed on the Simulator without problem.

  If I remove the splash screen images & icon in the Bar descriptor file, the application load on my Z10 with success.

  The images are the right size: 114 x 114 px for the icon and 768 x 1280 px for the SplashScreen.  The Momentics IDE accepts two files by activating beside them.  I also tried to add the images to the Q10 & PlayBook and still no luck with this loading on my device.  I even tried to go back to the image by default for the icon, and who does more either.

  The error I get when trying to install my application on my Z10 with icon images & Splash Screen is:

  Failure of deployment: Info: request shipment: install and launch
  Info: Action: install and launch
  News: Native debugging: on
  Info: File size: 414105
  Info: Installing com.example.ProfitCalc.testDev__ProfitCalc9866a36a...
  Info: Treatment 414105 bytes

  Someone has any ideas why this happens?

  Thank you.

  It is a known problem with certain versions of BlackBerry OS 10.1.  This article explains the problem and provide a workaround.

  Deployment of applications may crash or not after OTA 10.1 update.

• Bar is not signed RDK bar isn't signed AUTHOR this bar contains unsigned entries that did not check integrity.

  I created an application with qt creator, it works very well on my z10. But when I download the bar file to blackberry, I got this message

  "Bar is not signed RDK bar isn't signed AUTHOR this bar contains unsigned entries that did not check integrity.". "

  I am registered already BlackBerry signing authority and I also have a debug_token.

  The qt project has to a file of bar - descriptor.xml, information of the author are the debugging token.

  Can someone tell me how I can solve this problem?

  Problem solved.

  use the following two command lines

  BlackBerry XXXXX.bar bar-descriptor-XXXXXX-qtc-nativepackager-package - generated.xml

  BlackBerry-sign - storepass yourstorepass XXXXXX.bar

• Difference in size between Simulator .bar vs device-release .bar

  So, finally, I created my first app and I have a lot of trouble hell ship. so, here are the steps to generate the file bar. (using qnx momentics 2.0)

  1) click Project, and then export to another directory

  (2) import these files into a new workspace.

  (3) right click on the project and change the device-release build configuration

  (4) construction project

  (5) use bar - descriptor.xml for the Release version of export

  (6) create a folder as packer BAR and it has the bar of the file with arm / o.le - v7 (not sure what that means?). the file size is about 470 K.

  But if I do the same step and instead use Simulator-debug, the file size is about 1.6 M.

  When I click on the bar of file for the two build configurations, he settled on the Simulator (didn't have not a device to test, so using the Simulator to test the bar device-release file). Interestingly, file bar Simulator works fine, but the bar device-release file locks up.

  is this expected behavior, or am I missing something here?

  Thank you

  It is expected that the bar version file is much smaller than the debug bar file.  The debug version contains a bunch of extra stuff for debugging.

  A generation of device (debug or release) will not work in the Simulator as the Simulator requires an x 86 version and the real peripheral ARM version of the binaries.

  I don't know why you should export your project and import again to do a release build.  What happens when you try on your original project?