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-20-2012 06:18 PM
I am developing a bb10 app using BlackBerry 10 WebWorks SDK 188.8.131.52 and BlackBerry Ripple Emulator 0.9.8 Beta. <access uri="*" subdomains="true" /> is defined in config.xml file.
XMLHttpRequest worked before but I got the following message since this morning.
XMLHttpRequest cannot load
09-21-2012 04:13 AM
Did you try to disable the Cross Domain Proxy in Ripple? I had the same issue, but I wasn't sure the proxy worked in past. It seems has some problems with this feature.
09-24-2012 12:32 AM
09-24-2012 03:12 AM - edited 09-24-2012 03:13 AM
Do you open chrome by adding the option --disable-web-security in command line? Without this chrome will block your call.
There is a nice tool called curl to check your target service is responding. If it works with curl you could suspend all external issues. (That means it has do by something in browser)