Adobe-Runtime-Support icon indicating copy to clipboard operation
Adobe-Runtime-Support copied to clipboard

[ISSUE] Application changed render behaviour after 51.1.3.12

Open bobaoapae opened this issue 5 months ago • 4 comments

Prints from app running with 51.1.3.10

Image

Image

Prints from same app, just upgrade to 51.1.3.12

Image

Image

The same happens using 51.2 release

Also this appears to only happen on android, tested on windows and on mac and application appears to don't show any visual diff like on android

bobaoapae avatar Jun 24 '25 22:06 bobaoapae

Do you use BitmapData.draw() at all in the composition of those screens? We had put in a fix for a problem there, see #3729. Alternatively if you're using Context3D.drawToBitmapData(), a change happened to correct y-flip happening (see #392).

Are you using Stage3D? If you're not then do you see any difference if you switch renderMode between 'direct' and 'cpu'?

thanks

ajwfrost avatar Jun 25 '25 04:06 ajwfrost

This screen it's build using morn https://github.com/yungzhu/MornUI

I just create the screen using tool, and I get some output files to use in my project, I don't know for sure if it's using bitmapdata.draw or not. But I know for sure that this it's pure native stage, no stage3d involved

bobaoapae avatar Jun 25 '25 04:06 bobaoapae

Okay - probably if I can send you a test zip that outputs some logcat traces, we can see if this is caused by the BitmapData.draw update and whether we can work around it..

thanks

ajwfrost avatar Jun 25 '25 06:06 ajwfrost

Sure, I will wait for the test zip.

bobaoapae avatar Jun 25 '25 14:06 bobaoapae

@ajwfrost hello, any news on that?

bobaoapae avatar Jul 23 '25 17:07 bobaoapae

Hi @bobaoapae - we'd looked at the logs you'd provided from that test build but it didn't seem to show them, which either means we had something wrong in our test package, or it wasn't actually hitting those code paths...

So I think we'll have to send another version; we can perhaps try to isolate the individual change that caused the problem, I know which change I think is the culprit so perhaps we can do a 51.1.3.12 release plus that one patch to just confirm that this is what breaks it...

thanks

ajwfrost avatar Jul 25 '25 05:07 ajwfrost

Actually I just realised, it was working in .10 and failing in .12 .. but the change I had thought may cause the issue was introduced between those, so we've just reverted that (and added logcat output if it had been hit) so are you able to try with the test build please and see if it fixes things? (Build is being sent direct via the transfer system..)

thanks

ajwfrost avatar Jul 25 '25 07:07 ajwfrost

Hello, I tested this now and not fixed the issue. Replied the email with the logcat file

bobaoapae avatar Jul 25 '25 18:07 bobaoapae