Android™ Runtime Development

[nraboy]

Hi,

My users have been seeing an error in one of my apps that I cannot reproduce in the simulator.

My user is using BlackBerry Playbook OS 2.1 and my simulator is OS 2.1 as well.

The exact error is as follows:

java.lang.NoClassDefFoundError: com.mysql.jdbc.ResultSetImpl

This was a ported Android application.

When running the command line tools to convert to bar I only received two WARNINGS:

1. Icon was not appropriate size

2. Targetting ADK 15 instead of 10

The rest of my app performs as normal on the device according to my user.

I decompiled the bar file and found that com.mysql.jdbc.ResultSetImpl does in fact exist.

Why would my app fail to function correctly on the device when it works perfectly fine in the simulator?

Any feedback is appreciated.

Thanks,

[nraboy]

Bumping this.  Been two weeks with no response still.

[nraboy]

I received the following on November 1st in response to an email I made to BlackBerry.

---

Hello Nic,

Thank you for contacting BlackBerry Application Development Support.

Please wait for the ticket to be picked up and/or post to the forums if immediate support is required:

http://supportforums.blackberry.com/t5/Developer-Support-Forums/ct-p/blackberrydev

Regards,

Garett

Application Development Consultant

Application Development Support

Research In Motion Limited

http://developer.blackberry.com

Code Signing Problems? Try http://bbry.lv/oMzu93

---

I did as it said, but received no response on my Jira or the forum post.  I sent another email and got the following response on November 6th.

---

Hello Nic,

Thanks for posting to those locations. Your Issue Tracker item will be picked up in priority sequence and the forum entry should be addressed within a day or two as well.

Regards,

Garett

Application Development Consultant

Application Development Support

Research In Motion Limited

http://developer.blackberry.com

Code Signing Problems? Try http://bbry.lv/oMzu93

---

Since then my Jira is still unassigned and I have gotten no responses from BlackBerry staff on my forum post.  I've sent several followup emails and have received no response.  I thought BlackBerry is trying to keep developers by boasting their superior methods of support.  Where is this superior support?

Still waiting for a response.

[jdreher]

Hi nraboy,

Could you please provide some additional information as to the specific builds of PlayBook software being tested and reproduced on (simulator and device)? As well, can we determine if this behaviour being exhibited on the BlackBerry 10 Dev Alpha device/simulator?

[nraboy]

The simulator OS version is 2.1.0.1032.  The build for the simulator is 328132.

My user says he has the latest version of 2.1 on his device, but I will ask him for the specific build.

I don't see how me testing it on BlackBerry 10 is relevant.  My users don't have BlackBerry 10.  I'm trying to address the problem at hand before I adventure further.

I will post again when I receive the information.  Should be in about a day.

[nraboy]

The user having an issue has the following on his device.

OS: 2.1.0.1088

Build: 339713

That is newer than the specs I provided for the simulator.

Why am I experiencing these inconsistencies between the device and simulator?

[nraboy]

Bumping this again.  Am I going to have to wait another three weeks for a response?

The Jira is still unassigned.  It can be found here:

https://www.blackberry.com/jira/browse/TABLET-694

[nraboy]

Jira still unassigned and almost a week has passed since a BlackBerry representative has responded to this post.  No responses to my emails either.

Bumping this again.

[nraboy]

Bumping this again.

My emails, Jira, and tweets are being ignored.  Where is the support?

[jdreher]

Hello again nraboy,

My sincerest apologies for the delay, as this issue has been under investigation with our development team. This issue may relate to the app targeting Ice Cream Sandwhich rather than Gingerbread, which could have an negative effect on the com.mysql.jdbc.ResultSetImp class.

If you could DM me the app's link to App World, we can investigate the behavior of the app when compiled specifically for Android 2.3.3 rather than 4.0.