Build a release .bar

Similar Questions

• Build in-circuit debugging mode, but build in release mode fails.

  (crosspostes of https://developer.blackberry.com/html5/documentation/v2_2/build_and_sign_your_app.html#comment-17767... suite application to do here)

  In "%HOMEPATH%\AppData\Local\Research In Motion" I can see:
  bbidtoken. CSK
  (downloaded using my ID staff blackberry)
  barsigner.DB
  barsigner. CSK
  Author.P12
  (previously obtained and functional files for a provider - I signed WW1 and Momentics with these in the past)

  I have linked files as indicated by practice
  BlackBerry-sign - linkcsk - bbidtoken bbidtoken.csk - oldcskpass (password) - bbidcskpass (password)
  who responded
  News: CSK connected successfully to BBID

  When I try and build mode release web page, the following build log is displayed:

  [INFO] Target Q10-(pine) selected
  [INFO] The application of filling source
  [INFO] The analysis of config.xml
  [INFO] Generation of output files
  [INFO] Package created: (path)\simulator\bb10app.bar
  [INFO] Package created: (path)\device\bb10app.bar
  [INFO] Error: The file BBIDToken does not exist.
  [INFO] An error has occurred
  An error has occurred

  The message "BBIDToken file doesn't exist." is incorrect. There are still in 'C:\Users\username\AppData\Local\Research In Motion', and the two paths 'place' on the page "certificates" in the GUI Webworks web page point to the right place.

  A build command line "webworks build - version k (password)" gives the same "error: file BBIDToken not exist. ' error.

  Any suggestions where to go from here?  If this isn't '%HOMEPATH%\AppData\Local\Research In Motion', what directory the nonexistent bbidtoken.csk in?  I can verify that the "Info: CSK connected successfully to BBID ' really happened?

  It solved!

  The problem was that on the "Global settings" (not "certificates") page there is the following text:

  "Signing of the release certificate configuration.
  Location of developer certificate

  The file at this location will be used instead of a certificate installed for release builds. This location must contain the file name of the p12 file.
  Location of token BBID

  The file at this location will be used instead of a token BBID installed for release builds. This location must contain the file name of the csk file. »

  The text of the latter was "c:\Users\A.Townsend\AppData\Local\Research In Motion\bbidtoken.csk" (with a space left incorrect).  When I removed this text altogether, I got is no longer the "error: file BBIDToken not exist. ' error and a Release version work OK.  I didn't need a file of bbidtoken.csk; It worked OK with key legacy.  In turn, this means that my earlier review of http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-10-Code-Signing-Guide-for-C... is incorrect - the last article of this is correct for the old keys. you don't need to do anything else.

• 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).

• 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?

• Build the release version

  I just upgraded to the latest SDK and momentics after consuming not for a few months.

  I am now ready to build a version to download, but I don't see the option more.  I could have sworn that under the context menu of the project, under Blackberry tools there used an option to compile the version (who would sign and wrap it up).

  I think bad?  Is it deleted or moved?  Anyone know if it is still somewhere in the IDE?

  Nevermind, it's the title of export

• /Build/MTS/release/Bora-2249910/Bora/vmcore/VMX/main/timeTracker_user.c:234 bugNr = 148722

  After upgrade to Ubuntu, I got this kind of error. It is caused by the kernel.

  With the old 3.13 nuclei everything works as it should. New kernel 3.16 and I cannot start the VM.

  Tried to reinstall, same thing. Same 14.10 Ubuntu works very well with the same Wks 10.0.4, Vmware on my other PC.

  Attached log file.

  If you run the command

  Cat/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

  He output

  6300000

  ?  If so, the problem is between your operating system kernel, your firmware (EFI/BIOS) and your CPU.  We are given false data and there is nothing we can do about it.  You may be able to fix it with an update of the firmware for your motherboard.  It could be a defect in the new operating system kernel itself, or it could be that the more recent operating system kernel newly uses a new feature that is badly configured by the firmware of your host.

  If you need to substitute it, edit your/etc/vmware/config (as root) and add the line:

  host.cpukHz = 3467779

  and should you're going to get.

  See you soon,.

  --

  Darius

• Number of slides visited compared to the total number of slides? To build the progress bar %.

  I would like to put a progress indicator on each slide indicating the percent of the total number of slides that have been visited.

  

  To do that I need a variable that indicates the number of slides visitors (so not the number of THE slide that is ongoing).

  Any suggestions?

  OK, in this case, you need a variable user for each slide to be toggled

  from 0 to 1 on the first visit. Total number of slides visited is the sum of

  variables. There is no function to create the sum, you will need a sequence of

  Statements of the expression.

• Release date for CSA 4.02 build 629?

  This build has supposedly fixes the problem with the variable "@local" when using NACL.

  This build was released on May 13.

  There is a fix for the variable '@local' in build 629: use CSCee36266 @local issues after upgrade is no longer need second reboot.

  This fix meets your concerns?

  Please open a case with TAC or contact me offline at [email protected] / * / in order to get a link to the software.

  According to the product team, this is a minor version and not a typical maintenance release. This is why it does not appear in the typical location.

  Hope this helps,

  Peter

• DPS 2015 Build releases - must update us the signature tool?

  Every 3 weeks, a new build is released to 2015 DPS with new features and bug fixes.  When these new versions are released, should update us our signature tool and any other active provided Adobe DPS 2015 we can use?

  No need to update the signature only tool, it rarely changes. If/when he does it's usually just to provide better error messages for the signature of the errors we see in nature, no not to change the kernel that underlie the signature mechanism.

  If an update of the signature tool is necessary it would be listed in our notes.

  Neil

• Out of the build for only peripheral Q10 not for Z10

  Can I build a release for only Q10 peripheral and transfer it into the same product in BBWorld?

  If the device Q10 can see this build and Z10 sees the previous generation.

  Yes. During the download, you can specify which devices the file BAR is for.

• Output device - configuration of the handle bar not to change

  This question has me left speechless.

  Usually, I run the application using device-Release configuration. Yesterday, after construction with Simulator-debug, I turned back on build to release device configuration.

  Now I find that whenever I build the application, the active path in the bar - descriptor.xml automatically converted to the x 86 instead of arm/o.le-v7/. I can't run the application in release device mode now because of this automatic conversion.

  
         armle-v7
         lib/libBBCommonDatabase.so
         TestApp
     

  Clean up the project and build the project in the peripheral output mode before the race.

  I also facing the problem when I did as out of fashion Simulator to the peripheral debug mode.

  So try this one maybe it will help you.

• How to force the compilation released executable before running the distribution of LabWindows/CVI kit?

  I am new in 2015 of the CVI. I used CVI 7 and when I chose "Create the Kit of Distribution", when I was still in debug mode, Labwindows asked me to build the executable of setting before creating the Distribution Kit. This does not happen to CVI2015, and the Distribution Kit is created with the latest built executable version, although I made a few changes in my code! This is a problem since I work in debug mode and I usually forget to build the executable of liberation before calling the distribution kit, so I need CVI to do it automatically like CVI 7 did. I suppose that there is an option to do this, but I can't find. Can someone tell me please how to resolve this problem and force CVI to build the exe version before building the distribution kit? Thank you.

  Today, I've solved quite simply create a new distribution. The previous like unsing was automatically imported by CVI7 project. By creating a new distribution, now when I change something, CVI ask me if I want to build the release. So I did not understand the problem but I solved it by editing a new distribution kit.

• Build 64-bit DLL

  Hello

  I'm with LabWindows/CVI 9.0.1 (375) under Windows 7 64 bit and I need to build 64-bit DLL.

  According to this page http://zone.ni.com/reference/en-XX/help/370051P-01/cvi/programmerref/creating32bitappsversus64bitapp... "" "" I should have a menu build ' Configuration ' release x 64 or build ' Configuration ' Debug x 64 but I only have the option Debug and Release.

  Thanks for your help

  Yannick

  You need LabWindows/CVI 2009 to create 64-bit applications.

• Error in build Simulator target

  I'm new to BB 10 Web work 2, while trying to debug via Simulator, I get the following log?

  [INFO] The application of filling source
  [INFO] The analysis of config.xml
  [INFO] Generation of output files
  [WARNING] Cannot find the debugging token. If you have an existing token of debugging, copy it to C:\Users\Student\.cordova\blackberry10debugtoken.bar. To generate a new token of debugging, choose 'run '.
  [INFO] WARNING: Cannot find default icon or application
  [INFO] Package created: C:\Users\Student\WebWorks Projects\MyTime\platforms\blackberry10\build\simulator\bb10app.bar
  [WARNING] Cannot find the debugging token. If you have an existing token of debugging, copy it to C:\Users\Student\.cordova\blackberry10debugtoken.bar. To generate a new token of debugging, choose 'run '.
  [INFO] WARNING: Cannot find default icon or application
  [INFO] Package created: C:\Users\Student\WebWorks Projects\MyTime\platforms\blackberry10\build\device\bb10app.bar
  [INFO] BAR complete packaging

  Is there a Setup error in SDK?

  MShom, I was able to get a debugging managed without warning by bb10app.bar copy of C:\Users\Student\WebWorks Projects\MyTime\platforms\blackberry10\build\simulator in C:\Users\Student\.cordova file and rename it to blackberry10debugtoken.bar.

  Can I know why the bar file generated in the form bb10app.bar and BB10 WW2 application blackberry10debugtoken.bar?

  [INFO]    Populating application source
  [INFO]    Parsing config.xml
  [INFO]    Generating output files
  [INFO]    Warning: Cannot find application or default icon
  [INFO]    Package created: C:\Users\Student\WebWorks Projects\MyTime\platforms\blackberry10\build\simulator\bb10app.bar
  [INFO]    Warning: Cannot find application or default icon
  [INFO]    Package created: C:\Users\Student\WebWorks Projects\MyTime\platforms\blackberry10\build\device\bb10app.bar
  [INFO]    BAR packaging complete
  

• Problems to convert the APK in BAR

  Hello

  I have an Android application developed in Studio Android. When I convert to the BAR with Blackberry APK package, this is the output:

  [sne41 - release.apk]: found grouped in the APK apk2bar.prefs
  [sne41 - release.apk]: minimal.os.version = 10.3 preferably delivered using
  ([sne41 - release.apk] res/mipmap-xxxhdpi-v4/ic_launcher.png) found another icon with best size: impact = 1
  ([sne41 - release.apk] AndroidManifest.xml) contains metadata: com.google.android.maps.v2.API_KEY:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:127) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:27) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:93) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:96) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:117) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/civired/sne41/generaInfo/LocationActivity.java:117) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/AddPlaceRequest.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/PlaceEntity.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/zzd.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/zze.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/zzg.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/zzl.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/internal/zzr.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/ui/PlaceAutocompleteFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/ui/PlacePicker.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/ui/SupportPlaceAutocompleteFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/location/places/zzb.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/CameraUpdateFactory.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/CameraUpdateFactory.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/GoogleMap.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/GoogleMap.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zze.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzl.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzn.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/GoogleMapOptions.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/GoogleMapOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/MapFragment.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/MapFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/MapView.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/MapView.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/MapsInitializer.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/Projection.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzx.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanorama.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanorama.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzw.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzy.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzz.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaFragment.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaOptions.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaView.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/StreetViewPanoramaView.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/SupportMapFragment.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/SupportMapFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/SupportStreetViewPanoramaFragment.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/SupportStreetViewPanoramaFragment.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/UiSettings.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/ICameraUpdateFactoryDelegate.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/IGoogleMapDelegate.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/IMapFragmentDelegate.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/IProjectionDelegate.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/IStreetViewPanoramaDelegate.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/IStreetViewPanoramaFragmentDelegate.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzad.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzc.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/internal/zzt.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/BitmapDescriptorFactory.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/CameraPosition.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/Circle.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/CircleOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/GroundOverlay.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/GroundOverlayOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/IndoorBuilding.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/IndoorLevel.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/LatLng.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/LatLngBounds.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/Marker.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/MarkerOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/PointOfInterest.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/Polygon.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/PolygonOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/Polyline.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/PolylineOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/StreetViewPanoramaCamera.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/StreetViewPanoramaLink.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/StreetViewPanoramaLocation.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/StreetViewPanoramaOrientation.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/Tile.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/TileOverlay.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/TileProvider.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/TileOverlayOptions.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/zzi.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/UrlTileProvider.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/VisibleRegion.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/IPolylineDelegate.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/zzb.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/zzc.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/zzf.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/internal/zzg.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zza.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzb.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzc.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzd.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zze.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzf.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzg.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzh.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzi.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzj.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzk.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzl.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzm.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzn.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzo.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/model/zzp.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/zza.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/zza.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/zzb.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/maps/zzb.java) uses the package: com.google.android.gms.maps:impact = 4
  ([sne41 - release.apk] com/google/android/gms/wallet/wobs/zza.java) uses the package: com.google.android.gms.maps.model:impact = 4
  ([sne41 - release.apk] com/google/android/gms/wallet/zzk.java) uses the package: com.google.android.gms.maps.model:impact = 4
  [sne41 - release.apk]: Resizing icon ic_launcher.png 167 x 167-> 114 x 114
  [sne41 - release.apk]: config file missing PUSH: sne41 - release.cfg: impact = 3
  [sne41 - release.apk] summary: [5] = 0; [4] = 115; [3] = 1; [2] = 0; [1] = 1;
  [sne41 - release.apk]: generated log file: /Users/programador/Documents/APKs/sne41-release.wrn
  [sne41 - release.bar]: BAR successfully generated

  [sne41 - release.bar] igning began

  Information: The bar has been signed.
  Starting from blackberry - deploy - gui /Users/programador/Documents/APKs/sne41-release.bar - noSync
  Info: Application-Development-Mode is set to false, off sync
  Info: Send request: INSTALL
  Info: Action: install
  Info: File size: 9363590
  Info: installation...
  Info: Treatment 9363590 bytes
  News: Progress 0%...
  News: Advance of 60%...
  News: Progress 100%...
  actual_dname::com.civired .sne42 .gYABgPVb .VDLy706dHhzSaNy6v0
  actual_id:gYABgPVb - VDLy706dHhzSaNy6v0
  actual_version::1.0.8.0
  result::success

  When I run in the Simulator, APP crash automatically. I have no more information about the errors. How can I solve this problem? Can someone help me? Thank you very much

  @hmartinez do not select min OS 10.2.1 (10.3 will be fine).

  The question is that if you select 2.0 or less and supported of the PlayBook as a device, we need to test the application on this platform. If it fails, the entire application will fail.

  Please PM me your appID so I can study the issue further away.

  Finally, app control may take up to 5 working days, but we do not believe that it takes this long. If you experience delays of 4 days (not counting weekends), I'd be happy as climbing as well.