Android App Woes

jonathandlynch at gmail.com jonathandlynch at gmail.com
Mon Aug 14 05:02:35 EDT 2017


For the moment, is it sufficient to move turning on accelerated rendering to the end of the startup routine?

Sent from my iPhone

> On Aug 14, 2017, at 12:54 AM, Dan Friedman via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Jacque,
> 
> I don’t think I can make a bug report yet.  I don’t have it isolated outside my project; which LC will surely tell me to do!   I’ll work on trying to isolate the issue.
> 
> What I know is this:
> (1) My project runs perfectly with acceleratedRendering enabled – except when the app is suspended, it crashes when brought to the foreground again.
> (2) I put a button in my app with one line, it simply disables acceleratedRendering.  When I tap this button, the app no longer crashes when brought to the foreground after being suspended.
> 
> I am not really sure where to go to try to isolate the issue.   There is something definitely up with acceleratedRendering on Android.  On iOS, I enable acceleratedRendering at the beginning of my startup routine.  Works great.  On Android, this makes the app hang.  But, if I move the enabling of acceleratedRendering to the end of the startup routine, it works fine.  I had a related issue with setting the textFont of the mainStack at startup (we’re using an external font).  When I set the textFont of the stack after setting the acceleratedRendering, the app crashed.  But, setting the textFont of the stack before setting the acceleratedRendering was fine.
> 
> This is kind of a high-profile client and I’ve got about 1 week to get this resolved before I have to deliver the final app.  This must get resolved this week!
> 
> -Dan
> 
> 
> 
>> Please enter a bug report about this, it's a different issue than the one I wrote up.
>> 
>> --
>> Jacqueline Landman
> 
> 
> On August 13, 2017 1:07:12 PM Dan Friedman via use-livecode
> <use-livecode at lists.runrev.com<http://lists.runrev.com/mailman/listinfo/use-livecode>> wrote:
> 
>> I took Ralph’s advice and made a 0 line stack to try to recreate the issue.
>> To my astonishment, the app didn’t have the same problem!   So, I went
>> back to my project and started to trace what I have in my app that might be
>> causing the problem.   After a while, I discovered that if I do not enable
>> acceleratedRendering, the app does not bail on suspend and stays in memory.
>> Problem solved!   Except that I can’t leave acceleratedRendering off.  All
>> the scrollers stutter horribly!
>> 
>> I went back the test app and enabled acceleratedRendering.  But, it doesn’t
>> have the same problem.  I am most puzzled.
>> 
>> Help!
>> 
>> -Dan
>> 
>> 
>> 
>>> I have built my android app with LC 8.1.5.   It runs fine on the device.
>>> You then hit the home button to return to the OS.  Tap the app icon
>>> again and you get “Unfortunatly, [appName] has stopped.”.  Tap the icon
>>> again and
>>> it does a complete reboot of the app.   Apps made in LC 7 did not have this
>>> issue, they stayed running in the background – like an app should.   Is
>>> there a trick to getting an Android app from LC 8.1.5 to behave like it should?
>>> 
>>> I can’t deliver an app to my client that (a) doesn’t stay alive in the
>>> background, and (b) crashes every other launch.
>>> 
>>> Anyone have any insight on this??
>>> 
>>> -Dan
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the Use-livecode mailing list