Text inputs generate stack traces about adobe-runtime-support HOT 3 OPEN

Just to confirm that this is what I think it is ... are you able to confirm if you have the runtimeInBackgroundThread setting in your application descriptor XML file, set to true? And these errors would presumably go away if this was set to false?

We've added some protection already for some functions but maybe not all, I'll review these to ensure we're not getting caught out (the issue happens due to the async nature of these calls now, because we are running AIR in a background thread but a lot of these UI updates have to then be in the main thread, and there's not sufficient coordination or thread-safety between these)

thanks

from adobe-runtime-support.

We did not have runtimeInBackgroundThread explicitly set. Trying both false and true does not change the functionality we are seeing.

from adobe-runtime-support.

Okay thanks -> belatedly investigating and finding that the changes we made in also to support the asynchronous runtime on Android, also means it's impossible to take a StageText element off the stage and then add it back later on. The same root cause as this -> we lose a reference to the underlying 'AndroidStageText' class when it's removed from the stage...

Will get this into our next release!

thanks

from adobe-runtime-support.