Impossible to debug on real device

Similar Questions

• Impossible to debug with 9000 device

  Hi, I develop a little app that I debug in the Simulator and now I wan't to test on a real device.

  I have connected my BB Bold 9000 to the Pc via the USB cable and selected "join" in the JDE.

  Currently, I get lots of messages like "cannot find NET_RIM_APPMANAGER. DEBUG ".

  If I navigate to the directory of Simulator and select this file, then I0ve has received the message "(debugging information Bad C:\program files... \net_rim_appmanager.debug(4873cc83)-net_rim_appmanager (48c06f7e).

  I think the problem is a version mismatch, I downloaded the last Simulator ("version 4.6.0.92 (9000 Telefónica)"), but if I look in my camera in options-> it reads: "Blackberry 9000 (3G, Wi - Fi) V4.6.0.147 (Platform 4.0.0.144)".

  So, how can I get the files of debugging for the version V4.6.0.147 or how can I downgrade my V4.6.0.92 device?

  THX in advance for your help

  Concerning

  Alejandro

  Well, everything is now resolved.

  I found this post explaining that, sometimes, the JDE errors the need for signatures of a code particularly (in may cases, says JDE he needed RBB, but also RRT.) Thus, the .csl file editing and adding 52525400 = RIM API execution it compiles and runs correctly.

  So now that the code is executed, I can debug, even with the missing .debug files.

  Thx for your help, and I hope this can help someone else...

• How to debug on a real device?

  Hello everyone,

  I'm a new java developer using Eclipse plug-ins. every time when I had mistakes, only to debug codes on the Simulator, but I want the debugging on a real device. I already sign with BlackBerry $ 20. You guys can tell me how, please?

  Thank you

  Concerning

  In Eclipse:

  - Run > Debug Configurations...

  -Click Terminal BlackBerry on your left and then click the new (blank page with star.

  - Check the projects you want to deploy on your device.

  -Click the general tab and select debugging under "display in Favorites menu".

  -Make sure that your device is connected, and then press the debug button.

  -In the future, looking for a Bug icon in your toolbar, and then click the arrow next to it, then click on your project.

• HttpPushDemo throws the error of missing on real device resource

  I am trying to run the example of httppushdemo on a real device to test for problems with an application to push.  However, if I run the application in the device, I get the error "Missing resource com.rim.samples.device.resource.HTTPPushDemoRes.

  I looked everywhere to find out how to get the resource on the device and impossible to find a solution.  The documentation I found would lead me to believe that it should be compiled in the Cod.

  Why I'm so confused (and frustrated after a long day of our push to debug problems)

  Thank you

  -Bill

  In older levels (4.3 and earlier OS), RIM ran the code, so that the resources (labels field, the names of menu etc.) where in a separate package.  It's a good way to demonstrate how you could internationalize applications, but also everyone confused because putting the application on the device, you need to charge upward of the cod resources as well.

  At the latest OS (4.5 +), they do not do this.

  The demo of http push has not changed, so you can take the source of the 4.5 or later in a previous level JDE and compile it.  It will take so NOT all external files of cod.  That's what I recommend you do.

  However, for you to win download the JDE together for a single file, it is here:

  /**
   * HTTPPushDemo.java
   *
   * Copyright © 1998-2008 Research In Motion Ltd.
   *
   * Note: For the sake of simplicity, this sample application may not leverage
   * resource bundles and resource strings.  However, it is STRONGLY recommended
   * that application developers make use of the localization features available
   * within the BlackBerry development platform to ensure a seamless application
   * experience across a variety of languages and geographies.  For more information
   * on localizing your application, please refer to the BlackBerry Java Development
   * Environment Development Guide associated with this release.
   */
  
  package com.rim.samples.device.httppushdemo;
  
  import java.io.*;
  import javax.microedition.io.*;
  import net.rim.device.api.ui.*;
  import net.rim.device.api.ui.component.*;
  import net.rim.device.api.ui.container.*;
  import net.rim.device.api.system.*;
  import net.rim.device.api.util.*;
  import net.rim.device.api.io.http.*;
  
  /**
   * The client side of a simple HTTP Push system.
   * This application will listen for image data on the specified port and
   * render the data when it arrives.
   */
  public class HTTPPushDemo extends UiApplication
  {
      // Constants ----------------------------------------------------------------
      private static final String URL = "http://:100"; // PORT 100.
      private static final int CHUNK_SIZE = 256;
  
      // Members ------------------------------------------------------------------
      private ListeningThread _listeningThread;
      private HTTPPushDemoScreen _mainScreen;
      private RichTextField _infoField;
      private RichTextField _imageField;
  
      public static void main(String[] args)
      {
          HTTPPushDemo theApp = new HTTPPushDemo();
          theApp.enterEventDispatcher();
      }
  
      // Constructor --------------------------------------------------------------
      public HTTPPushDemo()
      {
          _mainScreen = new HTTPPushDemoScreen();
          _mainScreen.setTitle(new LabelField("HTTP Push Demo" , LabelField.USE_ALL_WIDTH));
  
          _infoField = new RichTextField();
          _mainScreen.add(_infoField);
  
          _mainScreen.add(new SeparatorField());
  
          _imageField = new RichTextField();
          _mainScreen.add(_imageField);
  
          // Spin off the listening thread.
          _listeningThread = new ListeningThread();
          _listeningThread.start();
  
          _infoField.setText("HTTP Listen object started");
  
          pushScreen(_mainScreen);
      }
  
      // Inner Classes ------------------------------------------------------------
      private class ListeningThread extends Thread
      {
          private boolean _stop = false;
          private StreamConnectionNotifier _notify;
  
          public synchronized void stop()
          {
              _stop = true;
              try
              {
                  // Close the connection so the thread will return.
                  _notify.close();
              }
              catch (IOException e)
              {
                  System.err.println(e.toString());
              }
              catch (NullPointerException e)
              {
                  // The notify object likely failed to open, due to an IOException.
              }
          }
  
          public void run()
          {
  
              StreamConnection stream = null;
              InputStream input = null;
              MDSPushInputStream pushInputStream=null;
  
              while (!_stop)
              {
              try
                  {
  
                      // Synchronize here so that we don't end up creating a connection that is never closed.
                      synchronized(this)
                      {
                          // Open the connection once (or re-open after an IOException),  so we don't end up
                          // in a race condition, where a push is lost if it comes in before the connection
                          // is open again. We open the url with a parameter that indicates that we should
                          // always use MDS when attempting to connect.
                          _notify = (StreamConnectionNotifier)Connector.open(URL + ";deviceside=false");
                      }
  
                      while (!_stop)
                      {
  
                          // NOTE: the following will block until data is received.
                          stream = _notify.acceptAndOpen();
  
                          try
                          {
                              input = stream.openInputStream();
                              pushInputStream= new MDSPushInputStream((HttpServerConnection)stream, input);
  
                              // Extract the data from the input stream.
  
                              DataBuffer db = new DataBuffer();
                              byte[] data = new byte[CHUNK_SIZE];
                              int chunk = 0;
  
                              while ( -1 != (chunk = input.read(data)) )
                              {
                                  db.write(data, 0, chunk);
                              }
  
                              updateMessage(data);
  
                              // This method is called to accept the push.
                              pushInputStream.accept();
  
                              input.close();
                              stream.close();
  
                              data = db.getArray();
  
                          }
                          catch (IOException e1)
                          {
                              // A problem occurred with the input stream , however, the original
                              // StreamConnectionNotifier is still valid.
                              System.err.println(e1.toString());
  
                              if ( input != null )
                              {
                                  try
                                  {
                                      input.close();
                                  }
                                  catch (IOException e2)
                                  {
                                  }
                              }
  
                              if ( stream != null )
                              {
                                  try
                                  {
                                      stream.close();
                                  }
                                  catch (IOException e2)
                                  {
                                  }
                              }
                          }
                      }
  
                      _notify.close();
                      _notify = null;   
  
                  }
                  catch (IOException ioe)
                  {
                      // Likely the stream was closed. Catches the exception thrown by
                      // _notify.acceptAndOpen() when this program exits.
  
                      if ( _notify != null )
                      {
                          try
                          {
                              _notify.close();
                              _notify = null;
                          }
                          catch ( IOException e )
                          {
                          }
                      }
                  }
              }
          }
      }
  
      private void updateMessage(final byte[] data)
      {
          Application.getApplication().invokeLater(new Runnable()
          {
              public void run()
              {
                  // Query the user to load the received message.
                  String[] choices = {"Ok" , "Cancel" };
  
                  if ( 0 != Dialog.ask("New message received. Do you want to render it?" , choices, 0) )
                  {
                      return;
                  }
  
                  _infoField.setText("Text received - size:  " + data.length);
  
                  try
                  {
                     _imageField.setText(new String(data));
                  }
                  catch (Exception e)
                  {
                      Dialog.inform(e.toString());
                      System.err.println(e.toString());
                  }
              }
          });
      }
  
      protected void onExit()
      {
          // Kill the listening thread.
          _listeningThread.stop();
  
          try
          {
              _listeningThread.join();
          }
          catch (InterruptedException e)
          {
              System.err.println(e.toString());
          }
  
      }
  
      private class HTTPPushDemoScreen extends MainScreen
      {
  
          /**
           * @see net.rim.device.api.ui.Screen#close()
           */
          public void close()
          {
              onExit();
  
              super.close();
          }
      }
  }
  

• Debugging on the device?

  Newbie here. I'm finally able to debug on a real device, 9330 which shows:

  6.0 bundle 2333 (v6.0.0.524, platform 4.4.0.438)

  I write apps targeting the 5.0 SDK. I guess from the above that the camera itself is version 6.0.0.524, is this correct?  So where can I get the specific Simulator for this?  None of the 4 last digits Curve 9330 simulators match. (I am trying to eliminate all the 'cannot find debug file"nonsense!) is there any detailed white papers on debugging on the correct device?  Also, I try to use Eclipse.

  Thanks in advance!

  All available BlackBerry smartphone simulators are available for download here: http://us.blackberry.com/developers/resources/simulators.jsp

  It may not be a release of Simulator for all versions available for download.  But we are always adding more, so you can keep an eye on this page for updates.

• Is it possible to intercept all start them console.log messages on real device using web Inspector?

  I'm trying to debug initiaization Stadium on a real device.  The problem is that I won't be able to establish a remote debugging session until the application is running.  And by then, I miss any message on the console that I have put in my initialization codes. Is there a technique to catch all console messages?

  In Web Inspector, you can also press CTRL + r to trigger a cooldown.

• my app works in ripple, but not in real device :(

  I made a request of 'fitness' with webwork development,

  It works very well in ripple and build, with success.

  but BB app world answer me it shows a blank page so it rejected, & I shocked when seen on real device from my friend did not work and the really white page

  I do not know

  how it works well on the training and do not work on the real device!

  Good luck.  If you're stuck on how to do it, here is the complete documentation on how to perform debugging using Web Inspector:

  https://developer.BlackBerry.com/HTML5/documentation/web_inspector_overview_1553586_11.html

• Screen orientation: real device vs. Simulator

  Hey guys (and girls).

  So yesterday when I got the SDK and harry first noticed a problem of orientation. To be honest, I couldn't even turn the unit in the Simulator (subsequently discovered click and drag). in any case, my current application is built assuming that we don't see rotation capabilities in the Simulator until later. But now that we have received the Simulator updated we can finally do some tests of rotation. So here's what we found:

  After you have added the following lines to the file - app.xml:

  false
  landscape
  

  I compile and run my app in debug mode in the Simulator. Works without a hitch. I do the click and drag the motion to rotate the Simulator. Does not work. Now I'll assume that this happens because I put the autoOrient false value. So now so far so good. If the user decides to rotate the unit while using my app it would remain the same (I was intending to do the portrait of mode changes later).

  So what's the problem. After I slide up on my request to minimize it while remaining in the fashion landscape, it appears as a normal horizontal application. Now if I were to click and drag the motion to make rotate the Simulator Simulator rotates - but not my application. Now, because it was shot all being reduced at least my application is still assuming that the device is in landscape mode and rest in the same form. Now when I maximize my app while still in portrait mode, it looks pretty bad to say the least. an application of landscape in portrait form factor - not a pretty picture.

  In the case where I have everybody scratching their heads, here are the steps to re - create (that's all assuming that your application is set to show only in landscape mode):

  1. Make a wonderful app
  2. Put the above code lines in your - app.xml file to avoid the orientation change.
  3. Compile and run / debug your application on the Simulator
  4. Assuming that your Simulator has not frozen (har har ) try to rotate the screen.
  5. After finding out, you are not able to rotate the screen, minimize your application with a sliding upward.
  6. Now turn your Simulator via the drag and turn motion (lower right in the middle of the screen)
  7. Now look at the way that your minimize the looks of the app.
  8. Maximize your single app landscape.
  9. Cringe.

  If you followed the steps in this order, you should be able to understand now if you have not already before.

  so my question is, is the same expected behavior of the real device? or will a single minimized application landscape turned to always be in mode 'landscape' and not stretched to fit the portrait mode?

  Thanks for any information / suggestion / effort of collaboration in advance!

  (btw while typing this workaround came to mind where I could check the current ratio of the height and the width of the stage and the direction myself - I'll keep you posted!)

  Even here, I will just wait. It works perfectly in Android (sim and device) so here I will not write code to fix something that will be fixed when it comes out (they can't leave it like that)

• Impossible to debug in Eclipse

  Hello

  I'm trying to debug an application in a true smart phone BlackBerry. I use Eclipse for a 8703e with OS 4.2.1.110.

  When I run the debug option, he tell me that I lack the net_rim_app_manager.debug file. I saw on the forum I need to navigate to the folder of the Simulator and select the correct file. I tried with all version of Simulator and Eclipse always telling me that I don't have the right file. I've read elsewhere that I need the exact os version of the Simulator, but there is no RIM Web site. I use the 4.1.0.359 version so that the Simulator for the 8703e.

  If I ignore the error message, as I read in another post, debugging starts, but my breakpoints doesn't work.

  What can I do? Any ideas? I really need to debug on the real device, cause all works on the Simulator, but I have problem in the actual device.

  THX

  I found the problem! The version was not quite the same thing (only an IP in a change of HttpConnection) so the debugger do not stop.

  For all the people who have this problem, make sure you have the exact same version of the application installed and use in Eclipse (do not add a space online!).

  Thx for the support

• How to develop and test the application mobile flex without the real device?

  I'm trying to read some information about it, but decided to ask also here.

  I have a project that has a company wants to grow me, it's for iPad. That's ok I am with Flex and the framework for web development, but not for mobile. Why? Because I have no idea how to test my application. I know generation ago it sort of the desktop version of the application with the change of the "back" button on the orientation stuff, but how do I know my application will look and work exactly the same (I mean NOT performance here). I mean you know how every android or iOS device have their native keyboard or native video player for example and I have only in the debug version of the application.

  The question is how to develop this application based on the desktop emulator or anything and then hope that my app looks and works on a device, as it should... Of course I can't afford to buy all the devices it is just to be able to test on it if necessary? So, how do you, how to test how my iPad app works on a device without a? I know I should get a licence from iOS dev to be able to package the app for iOS, but it's $ 99 per year or something like that I can handle, but how to test my application without having to buy the darn device? Are there any emulator for iPad or something like that I know what my customers will see when they get the application? One of my friends told me that the mac os x use the developers a tool - cause some kit of dev who has emulators for all iOS devices and you can build and test there immediately and that you can simulate virtually any combination of key for example, and he said he's working and seems to 1:1 as the real device but he didn't know if can I export an AIR application and try it like this, he only knew for app written in native code.

  If someone can just tell me how should I do this? Should I buy a mac os x computer laptop to test because I am a user of windows 7, or perhaps create a mac os x virtual machine and tests out there or maybe the only option is to actually buy the device... that would be terrible for a freelancer...

  I hope someone can save the day here! Thank you.

  F

  Since the AIR for iOS applications are compiled to ARM code you will not be able to run on iOS emulators running on Mac OSX.

  You can do a very simple test with the "Simulator" built into Flash Builder, but it is not much more than a window to AIR with a window size that matches the resolution of the selected iOS device.  When running in the simulator of the application is not compiled to ARM code so it will take a completely different code path than what will be the final release of iOS.

  Ultimately if you are developing for iOS with AIR nothing but for tests on real iOS devices.

• Council of softkey is not coming by clicking textfield on Simulator, it will show on real device

  I wore an android application for bb 10 app, here I am facing problems.
  1 key board is not coming by clicking textfield on Simulator, it will show on real device

  2. I want to show 6 pictures long in size on a page to display scrolling but memory is out of range

  Hello

  No. 1: If you started the Q10 Simulator, it is expected for the real device has a physical keyboard. The Simulator startup, select the Z10 and test again to get the virtual keyboard.

  2: this question would better fit for a new topic. In any case, a strategy would be to cut the long cards for the smaller pieces and loading them dynamically, effectively keep in mind a few.

• Google addresses on real device

  Hi guys,.

  I have an application that uses the API of Google Places which is https connection. It works fine on the emulator when I put specific ssl and https settings in the .rimpublic file:

  [HTTPS HANDLER]
  application.handler.https.allowUntrustedServer = true
  [TLS HANDLER]
  application.handler.tls.allowUntrustedServer = true
  application.handler.tls.logging = true
  

  BUT, when I run on the real device, https fails. What should I do to make it work on my phone? Where should I change these settings? It is up to the carriers and the RIM servers, or I can do in the application?

  Hello

  Here is an article that talks about the HTTPS on BlackBerry connection.  I hope this helps.

  http://supportforums.BlackBerry.com/T5/Java-development/BlackBerry-support-for-HTTPS-connection/Ta-p...

  Thank you

  Naveen M

• Eclipse pluging 1.1 - "debug as Blackberry device".

  I installed eclipse 1.1 pluging. Looks like it works more stable and faster.

  When I chose "Debug under"-> "Blackberry Device", IDE builds, signs, and download bionary on device. Cool!

  But due to the update of the app, the appliance resets and IDE cannot debug.

  Why the plugin is unable to wait for the reset? Can it be fixed?

  I was able to replicate this and it will apply to less than 5.0 BlackBerry device software.  Here is what actually happens:

  Debug as-> device BlackBerry deploys the application on your BlackBerry Smartphone and attaches it to the debugger.  However, replacing the application can cause the device reset, which disconnects the debugger.

  The workaround is to uninstall the existing application (Options, Applications) prior to a "Debug As-> BlackBerry Device", which will prevent the reset.

  I forwarded this question to our development team for resolution in a future release of the BlackBerry Java plug-in for Eclipse.  It was recorded in the handler incidents here: https://www.blackberry.com/jira/browse/TOOL-161

• Problem test on a real device - app does not start

  I use

  Eclipse 3.5 Galileo

  BlackBerry JDE 5.0

  BlackBerry Desktop Software 6.0.0.43

  a real device Curve 8900 with the software updated to 5.0.0.681.

  I read that Simulators have problems with Blackberry Maps. So, I wanted to test my application on the actual device to see if I've run into the same errors. Packaging and code-signing everything has worked well. I then installed the software on the device through Blackberry Desktop software. I found the icon in the downloads folder of the device but you cannot start the application. When I click on it nothing happens. No no error message, nothing, simply no reaction. So I have no idea what went wrong. Does anyone have an idea or suggestion how know what's the problem?

  I can start and run the program on the Simulator.

  Hi navad.

  I had the same problem a few days ago.

  Only the developed app one shows no reaction. all other things are working well.

  to me, helped the following:

  When the Blackberry is running, remove the battery and wait 2 minutes.

  Replace the battery and the blackberry again.

  After that, you should be able to run your application.

  I hope this will help.

  CU

  Michael

• Unable to connect to my real device webservice (KSOAP)

  Hello friends of BB,

  I wrote an application for my black berry. My application to connect to a PHP Web service. I use the ksoap library to connect to my webservice. It works on my Simulator, but when I add my request on my real device does not connect to my webservice. I think I need to add something to my url. I call this URL:

  final String url = http://www.*****.de/webservice/dbservice.php
  
  final HttpTransport http = new HttpTransport(url);
  
  ...
  

  I hope someone can help me.

  greeting

  Dennis

  See the sticky thread here.

  http://supportforums.BlackBerry.com/T5/Java-development/connecting-your-BlackBerry-http-and-socket-c...

  As you can guess, this question has been answered repeatedly asked.

  In short, the Simulator emualtes a device connected to BES (if MDS - CS is running), it is not necessary for URL parameters in this environment.

  However, once you get on a real device that is not connected to BES, you will need to do a bit of work to determine what types of connectivity are available and develop your parameters of connection accordingly.

  A direct TCP connection (for example) will require "; deviceside = true' + settings specific to the network of the AFN.

  See this article:

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800451/800563/What_Is...