airsdk / Adobe-Runtime-Support

Report, track and discuss issues in Adobe AIR. Monitored by Adobe - and HARMAN - and maintained by the AIR community.
203 stars 11 forks source link

[Android] Theme issues between Android 11 and 12 #2166

Open d-angelovski opened 2 years ago

d-angelovski commented 2 years ago

Problem Description

Trying out our app on android 12 gives weird results with theme (UI elements are missing, ex only 1 button shown, missing table borders on some pages etc)

See images in Android 12 with issues: image image

This images are on Android 11 and there is no issues at all like above:

image

image

I have tried also changing between Air SDK versions (795, 856, 889 and 929), different Java (8, 11 and 17), its the same issue.

Same build, on Android 11 is all ok. Target SDK used is 31.

I am not sure this is Harman issue, but there is some difference between Android 11 and 12, that is affecting our app in weird ways.

If anyone have any idea what to test or try in order to get more insight of the bug, or maybe what could be causing this I would be gratefull.

marchbold commented 2 years ago

What are you using to theme your app? Is it flex / starling / feathers, any native text fields?

d-angelovski commented 2 years ago

Sorry, havent seen your message untill now. It's Flex, Spark components.

dkjurchiska commented 1 year ago

The same issue on AIR 50. Works properly on 743 and 698. Flex - spark components. Can you advise how to resolved on AIR 50, because with older version we have OpenSSL issue on Google Play Store?

ajwfrost commented 1 year ago

Hi -> just checking here, if you build with 33.1.1.743 then the layout is fine on Android 12, and if you build it with 33.1.1.795 then you have these layout problems?

The obvious difference between these releases related to Android 12 was around the font settings..

Updating Android font rendering mechanism to work on Android 12

If you're just using English text, it may worth checking whether this is the issue or not: can you try adding the below flag into the "android" section of your application descriptor file?

    <newFontRenderingFromAPI>99</newFontRenderingFromAPI>

This should disable the new rendering code and leave you with the native skia code used earlier. If that works, then it means we have an issue with the Java-based font rendering still...

thanks

dkjurchiska commented 1 year ago

Hi, yes I can confirm that there are differences in fonts between 743 and newer version, I will try that tag. Thank you very much and let us now when rendering issue will be resolved to use our font.

If it helps, we use:

Verdana fonts/verdana.ttf VerdanaBold fonts/verdanab.ttf
ajwfrost commented 1 year ago

Hi @dkjurchiska - would you be able to create a simpler test app that demonstrates the problem here? as we've not been able to get this to reproduce when we're creating a test case from scratch. I suspect it's something going on in Flex relating to some properties that may change between these modes, but we've not found any differences yet!

thanks

CT-PDept commented 10 months ago

I am also seeing these issues. When I add <newFontRenderingFromAPI>99999</newFontRenderingFromAPI> to app-descriptor some of the fonts render correctly, but it doesnt render properly on other parts of the app. I am not sure what I should do to resolve this issue.