11-29-2012 05:09 PM
My app is broken after upgrading to BB10 OS 10..0.9.1103 on my dev alpha and using Webworks 1.0.3.8 for BB10 to recompile (as was suggested). Aside from many small glitches, I have noticed now another important feature is not working:
"run_when_backgrounded" in my rim
ermissions section of the config.xml.
It was working *FINE* on the previous Webworks/BB10 OS and that is what I based my submission to Appworld on, was already approved and for sale and working beautifully. But now I recompiled using the latest Webworks SDK and this is not being followed.
Has the format for this XML file changed? I already changed the format for the landscape/portrait orientation XML, but why is my app not staying on after the default backlight timeout?
It is frustrating especially after working to get my apps polished and submitted that a version change would keep breaking key features without any solutions or work-arounds. I hope this feature hasn't been removed from webworks apps and javascript.
Any ideas? Help!
11-29-2012 05:10 PM
11-29-2012 11:44 PM - edited 11-29-2012 11:47 PM
Ok. I believe it has to do with my work-around to keep the backlight on, not the "run when backgrounded" option. The work around used a looping video element playing to keep screen on. Did RIM finally patch that hole?But where is the option to keep backlight on?
It was working fine in the previous OS. All I did was recompile without changing a line of code except for making webworks.js reference to local:///chrome/webworks.js.
Anyone know if there is a function implemented now in webworks to allow toggling the backlight timeout value? Or whether the video loop method should still work or was touched? Help! My app was successfully keeping the backlight on using that trick and so was my Playbook app... That was the only way that existed for webworks app to do this, because we didn't have any other way to do this.