Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
02-15-2013 09:11 AM
Thanks for the dump, now I see where the confusion comes from.
You are using unsupported library 'com.google.android.maps' which triggers verifier to log a warning.
However there is a bug in the verifier pointing to the only supported library 'android.test.runner' in the text instead of the found 'com.google.android.maps'.
Again thanks for the report and we have logged this issue.
06-17-2013 03:38 PM
This issue is now fixed in the 1.6 version tooling release. The online package will be updated soon to include these updates. Please let me know if you are still experiencing issues.
06-17-2013 04:12 PM
According to you AndroidManifest dump you are using:
There has been a bug fixed in our tools which cause confusion by listing wrong library name. It is already fixed in our recent release and you will see following warning message instead:
(AndroidManifest.xml) uses-library: com.google.android.maps:impact=4