Our workaround is to deploy a separate version of our app under the ST188.8.131.52 codeset. In all honesty it completely sucks having to maintain a second codeset to support the playbook, especially when we spent a lot of time migrating to using some of the enhancements in ST2.1, but it's all we have for now.
I've heard from some of my contacts in RIM that they MAY (fingers crossed) eventually migrate the Playbook to the BB10 OS, but I wouldn't hold my breath. I'm also not holding my breath that this bug is actually going to get fixed.
But I would love to have someone from Sencha weigh in!
Originally Posted by drlarsen
This bug report is flagged as a duplicate, however I can't find the original. Could someone point me to the original bug report?
Also, is there any way to find out the status of a fix? This bug completely breaks our app on Playbooks, which are listed as supported device. I'm hoping a fix or workaround will be available soon.