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.
09-17-2013 10:29 PM
Has any one been getting reports of App issues with the Leaked OS 10.2.0.1725
I got a handful of emails indicating that part of of my application is not working in this OS. I was just wondering if any one has encountered this issue?
09-18-2013 02:40 PM
You're able to test your application on 10.2 with either the simulator or the developer autoloader here - https://developer.blackberry.com/blackberry10deval
If it works on this it will should work on later builds of the OS. I'd be very suprised if it doesn't as the AIR runtime does not change.
Out of curiousity what parts of your application were reported not to work? Anything that you find odd?
09-18-2013 11:04 PM - edited 09-18-2013 11:06 PM
I downloaded the leaked OS 10.2.0.1725 and installed it onto my Dev Alpha C. I was able to reproduce the issue with the leaked OS 10.2.0.1725 and SDK 3.1.3. This issue does not exist with the Simulator version 10.2.0.1443
The issue is with the TextInput component. The stack trace is below. Updating my SDK to 3.2.1 resolves the issue below on the leaked OS.
Error: Skin Asset Class with identifier textinput_up does not exist! at qnx.fuse.ui.theme::ThemeBase/getSkinAsset()[E:\hud
son\workspace\BB10_1_X-AIR_SDK_API\src\qnxui\src\q nx\fuse\ui\theme\ThemeBase.as:74] at qnx.fuse.ui.theme::ThemeGlobals$/getSkinAsset()[E: \hudson\workspace\BB10_1_X-AIR_SDK_API\src\qnxui\s rc\qnx\fuse\ui\theme\ThemeGlobals.as:229] at qnx.fuse.ui.skins::UISkin/getAsset()[E:\hudson\wor kspace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse \ui\skins\UISkin.as:167] at qnx.fuse.ui.skins.text::TextInputSkin/getSkinForSt ate()[E:\hudson\workspace\BB10_1_X-AIR_SDK_API\src \qnxui\src\qnx\fuse\ui\skins\text\TextInputSkin.as :44] at qnx.fuse.ui.skins::UISkin/init()[E:\hudson\workspa ce\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\ skins\UISkin.as:121] at qnx.fuse.ui.core::UIComponent()[E:\hudson\workspac e\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\c ore\UIComponent.as:258] at qnx.fuse.ui.skins::UISkin()[E:\hudson\workspace\BB 10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\skins \UISkin.as:101] at qnx.fuse.ui.skins.text::TextInputSkin()[E:\hudson\ workspace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\f use\ui\skins\text\TextInputSkin.as:24] at qnx.fuse.ui.utils::DisplayObjectUtils$/createInsta nce()[E:\hudson\workspace\BB10_1_X-AIR_SDK_API\src \qnxui\src\qnx\fuse\ui\utils\DisplayObjectUtils.as :51] at qnx.fuse.ui.core::SkinnableComponent/setSkin()[E:\ hudson\workspace\BB10_1_X-AIR_SDK_API\src\qnxui\sr c\qnx\fuse\ui\core\SkinnableComponent.as:151] at qnx.fuse.ui.text::TextInputBase/init()[E:\hudson\w orkspace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fu se\ui\text\TextInputBase.as:660] at qnx.fuse.ui.text::TextInput/init()[E:\hudson\works pace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\u i\text\TextInput.as:232] at qnx.fuse.ui.core::UIComponent()[E:\hudson\workspac e\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\c ore\UIComponent.as:258] at qnx.fuse.ui.core::SkinnableComponent()[E:\hudson\w orkspace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fu se\ui\core\SkinnableComponent.as:77] at qnx.fuse.ui.text::TextInputBase()[E:\hudson\worksp ace\BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui \text\TextInputBase.as:586] at qnx.fuse.ui.text::TextInput()[E:\hudson\workspace\ BB10_1_X-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\tex t\TextInput.as:217]
09-19-2013 11:03 PM - edited 09-19-2013 11:05 PM
I just checked and the QNXSkins.ane is definitley packaged (3.1.1 SDK)... Anyways, I have not changed anything and it only causes an issue on the leaked OS. So it definitley seems to be an issue with the leak and 3.1.1SDK's Text Input control.
Dustin can you confirm?
09-20-2013 09:18 AM
Seeing how it's a "leak" I assume it didn't get properly tested and these kinds of problems are expected. Stick with making sure it works with what BlackBerry has provided developers and you shouldn't have anything to worry about..