03-05-2012 09:30 PM
I'm a little frustrated as my Android application works both native Android and the Simulator but gets rejected by RIM due to a force close at startup. Unfortunately I don't have a playbook and since RIM does not send a logcat back it makes diagnosing this issue close to impossible. So a couple of questions for the group:
1. There are obviously some bugs I assume with the simulator, does anyone know of any circumstances where an Android App works on the Simulator but not the physical device ?
2. Are there any other alternatives to the simulator (or physical device) to test this application - such as a sandbox environment available online (though not sure it would be any different then the simulator).
As far as I know my application is properly signed (RIM never complained)
Any insight would be greatly appreciated,
11-29-2012 10:28 AM
Do you have a local developer club where you can borrow a PB to test with? Friends with PB's maybe?
In my opinion when releasing an application for a particular device, you should test the app on that device specifically to catch any issues that do not surface when using simulators.
There are companies you can pay to have them test for you, but at that price you are better off just buying a PB.
Like all my posts, and mark them as the solution if it solved your problem.
My Website: Paolo Rodriguez
12-03-2012 09:08 PM