Strange bug when coming back to app

I am porting my Steam game Plantera to the mobile and have run into a few issues. I have come across a very strange bug that is happening on the Android where if I boot up the game everything is normal, but if I leave the app, by clicking the home button for example and then re-enter the app things start to show up wierdly, as far as I can see it seems to be connected to blitters that is supposed to display text, they show up strange and seems o have moved their position somehow. I have tried 3 different devices and it is the same on all of them.

Here is an example how it looks like normaly when you click on an icon to expand your garden: https://dl.dropboxusercontent.com/u/...1/5/Before.png

And this is how it looks like after you do the same after you have been away from the app and then re-enter it: https://dl.dropboxusercontent.com/u/4047131/5/After.png

This is really really strange and I have no idea what could cause it, have anyone come across anything like this and know what to do?

At least the bug is consistent.

Can you see if you can make a small little MFA of the problem and send it over to Fernando?

I will try to isolate a small example.

However I found out something more, this does not seem to have been happening in older builds. I tried to make a build now with my previous game Tap Heroes, and the same thing is happening in this game (especially look in the top right where it is supposed to read "extra shop" when I re enter the app, and also the letters and numbers in the stats screen get scrambled up): https://dl.dropboxusercontent.com/u/...-10_183126.wmv

However, when downloading the public build I have up on Google Play Store that I updated in October 2015 the issue is not there. I have tried to go to the home screen and re-enter the app and there is no bugs with the blitter. So this must mean this new bug has been introduced with a later build of Fusion or the Android exporter. I don't know what I build I used when doing the build in October though.

Btw, if I want to go back to an earlier build of the Android exporter to chec, is it enough to just install one of the older Fusion dev updates that is supposed to update all exporters at once? (for example cf25dev.b284.10) Also is there any way to check what current build you have installed of a particular exporter?

oh I did something to text are you using smooth resizing in your game? I remove totally antialiasing if is uncheck in android properites

build your game in release and send me a link for me to test here.

I don't use smooth resizing. Also the "text" is not actually text as in "strings", it is a blitter that create active objects to show up as letters.
I tried the file you sent though to be sure, but the issue is still there.
I am almost ready with a clean example that I will upload.

Ok I have now made a clean example of the bug.
In this example, click on the "Create" button to create a text, and then the "Destroy" button to destroy it.
Then to check out the bug, destroy the text and then leave the app and come back to it. Now when creating the text again it will be all bugged out.
Now when destroying the text and creating it again after the first time after coming back it will show up right again.
The reason I have to click twice when coming back is that the window loses focus for some reason when recording and going out and then in to the app.
Here is a video also showing the bug in action: https://dl.dropboxusercontent.com/u/...fterReturn.wmv

let me review your example, but strange no other change done in runtime.

thanks in advance for your example

------------------------------------------------------------------

can you try with a name with at least 3 letters "A0df", here seems to work.

"can you try with a name with at least 3 letters "A0df", here seems to work. "

Do you mean with 3 or less letters?

https://dl.dropboxusercontent.com/u/...-11_153033.wmv

I can confirm that there is indeed something that have been broken in later versions!

I installed an older version of Fusion v 283.5 and in this version it does work: https://dl.dropboxusercontent.com/u/.../5/Working.wmv

If I then install the latest version v 284.10 it breaks again.

Sorry, the name of the loop instead of "0" use a name with at least 3 letters like "A0d" or "A0df" and make your text as long as you can to test everything is ok.


or at least an alpha char in front of the number will do like A0

Tried to change the loop name to "A0df" but that had no effect.

It still works as it should in Fusion v 283.5 and breaks in v 284.10

What version of the Android exporter is in Fusion v 283.5 vs v 284.10?

Is there some library of older Android exporter versions so I can go back and see exactly in what version the bug starts to occur? I could not find many version in the owners lounge, and the older ones have broken dropbox links.

oh I am using the latest beta derived from 285.1 and work ok, but fastloop have not been change since 257 though.


I modify your example to be able to change the loop name


https://www.dropbox.com/s/3oirqf3pmj...modif.mfa?dl=0


this work here https://www.dropbox.com/s/mkyqmvepoz...eturn.apk?dl=0

can you tell me which idiom/language for input are you using in your test device.

Why do you think there is anything wrong with the fastloop name?

The bug is still there in your mfa if running on v 284.10: https://dl.dropboxusercontent.com/u/4047131/5/Newer.wmv
It works on v 283.5 though as usual.

I could not open your apk, I get an error: "inconsistent_certificates" , could this be because you signed the app for release?

Hmm what do you mean by idiom/language?
I have tested on a OnePlusOne, Andy and on a Pipo Tablet. On all of those the version I build with fusion v 283.5 work and if building on v 284.10 the bug occurs.

I updated the example to also display how many loops are run. It is the second counter below the first one.
There is 14 loops run when the text is created. There is also 14 loops run when the text is displayed wrong after coming back so there seems to be nothing wrong with running the loops, if that is why you thought to change the loop name?

https://dl.dropboxusercontent.com/u/.../5/NrLoops.wmv

Oh Outcast I cannot give fix to an old release, you need to tell me if it works in version 285.1 which is the latest release we are working on.

https://www.dropbox.com/s/o2jvrtf9qj...25335.mp4?dl=0

my test using betas based on 285.1

I just tested it and the bug is still there in 285.1.

Also Fernando, I looked at your video and you are not testing it properly. You need to leave the app, and then go back to it, that is when the bug occurs.
You can see in this video how to test it properly: https://dl.dropboxusercontent.com/u/.../5/Testing.wmv

I did not show it but I reenter several time and no error here, let find out what could it be, can you grab me a log from your device to check here

Are you sure you are doing it right? Could you record it when testing it out properly?

I have tested on 3 devices and it is consistently the same bug on all of them if building with v 285.1 or 284.10. And the bug is not there if going back to v 283.5 so it must be something that was done in later versions.
How do you mean grab a log from the device?

Tested on a 4:th device, and the same bug is there.

yes I finally got that at the 3 time but I got now, but I don't think is for loop I am debugging and the loop is returning the index correctly each time what changes is the initial location.

try this at your side, do you test normally, but send the application to background with the text, so you need to do a destroy before create, like this work always here.

also please put this as bug in bugreport system, as always thanks to get this bugs.

https://dl.dropboxusercontent.com/u/...turn_fvd01.mfa

this example as the right value of the blitter and the other string is the index from loop

Hmm I am not totally sure what you want me to test?
I recorded testing out this version you sent here: https://dl.dropboxusercontent.com/u/.../5/Numbers.wmv

Ok I think I narrowed down the source of the bug!!
It have nothing to do with loops etc, the bug occurs when returning to the app and creating an object and then creating another object and setting that objects X position "to the Right" of the other object!
I have made new clean example that is just 2 events to show this, it should be easy to narrow down the cause of the bug now I think.
What is more, it seems to work to set the objects X position to the Left of the other object, or the Y position to the Top or Bottom of the other object, it is just the "set to Right" that seems to be bugged for some reason.

Here is a new video showing the bug in action: https://dl.dropboxusercontent.com/u/.../SetPosBug.wmv

Yes, the problem is when you destroy an object and you go to background the texture are deleted and when you are back all texture need it are recreated but this object is not in the list to be recreated so it needs to be created first (but not in the same loop), see that the width is always 20 discard the fist time that is 0.

Fernando, I tested the Anroid runtime you posted in the bug box, and have some good and some bad news!
The good news is that the bug seemed to be solved! I tested with the small example mfa I made and it seemed to work as it should so that is great!
The bad news is that when trying to build my real app I am working on with this new Android runtime I get a build error:


Buildfile: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bu ild.xml

-set-mode-check:

-set-debug-files:

-check-env:
[checkenv] Android SDK Tools Revision 24.4.1
[checkenv] Installed at C:\Program Files (x86)\Android\android-sdk

-setup:
[echo] Project Name: RuntimeAndroid
[gettype] Project Type: Application

-set-debug-mode:

-debug-obfuscation-check:

-pre-build:

-build-setup:
[getbuildtools] Using latest Build Tools: 23.0.2
[echo] Resolving Build Target for RuntimeAndroid...
[gettarget] Project Target: Android 5.1.1
[gettarget] API level: 22
[echo] ----------
[echo] Creating output directories if needed...
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\res
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\rsObj
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\rsLibs
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\ge n
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\classes
[mkdir] Created dir: C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\dexedLibs
[echo] ----------
[echo] Resolving Dependencies for RuntimeAndroid...
[dependency] Library dependencies:
[dependency] No Libraries
[dependency]
[dependency] ------------------
[echo] ----------
[echo] Building Libraries with 'debug'...
[subant] No sub-builds to iterate on

-code-gen:
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[echo] ----------
[echo] Handling BuildConfig class...
[buildconfig] Generating BuildConfig class.

-pre-compile:

-compile:
[javac] Compiling 549 source files to C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\bi n\classes
[javac] warning: [options] source value 1.5 is obsolete and will be removed in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
[javac] C:\Users\VaragtP\AppData\Local\Temp\AndC831.tmp\sr c\Extensions\KcArrayActs.java:214: error: method openHFile in class CExtension cannot be applied to given types;
[javac] HFile hFile = thisObject.ho.openHFile(fileName);
[javac] ^
[javac] required: String,boolean
[javac] found: String
[javac] reason: actual and formal argument lists differ in length
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 3 warnings

BUILD FAILED
C:\Program Files (x86)\Android\android-sdk\tools\ant\build.xml:716: The following error occurred while executing this line:
C:\Program Files (x86)\Android\android-sdk\tools\ant\build.xml:730: Compile failed; see the compiler error output for details.

Total time: 4 seconds

oh sorry this runtime is attach for the new objects and change made for api 23, sorry, please let me know if you are using 285.1 to make an runtime for you

Thank you! I am using 285.1 right now and that version seems to be stable as far as I have seen so that should be good!
Or should I use api 23 also? Or is that not recommended to do yet?

mm no you can use betas and api 22 perfectly, I will send you a link with a new runtime compatible with 285.1 for you to try, but the good idea is to test betas so at the moment is release is full proof.

only when new editor is released with target 23 then will be possible to make full marshmallow application with full new permission system compatible, but again the new betas are backward compatible.

Thanks! The new runtime you sent seems to work now as far as I can tell! *cross fingers*
I have tested on a couple of devices and everything seems to work as it should now so good work! :D

Seems like I'm having a similar problem (using text blitting) - where can I get the fixed version?
Thanks!