breautek commented on issue #1616: URL: https://github.com/apache/cordova-android/issues/1616#issuecomment-1562177571
Was able to reproduce the issue locally. I believe this is a regression from our https://github.com/apache/cordova-android/pull/1550 update. I didn't notice it was an issue before since I have a `src` fallback. Until a patch is made, I think there are two workarounds: 1. Include a `src` attribute to your icons, which should be a full android drawable (either a rasterized PNG, and I believe android's AVD is also suppported). This will include icons for pre API 26 devices (and will also apply to API 26+ devices if the adaptive icons aren't present, which due to this bug they aren't). This of course has the caveat that your icons won't be adaptive icons and animations and such won't apply. 2. If you include a monochrome icon via the `monochrome` attribute which should lead to an android drawable that is a black and white version of your icon, then the adaptive icons do work as expected. API 33 devices with themes enabled will use this icon to produce a themeable icon that works in light mode, dark mode, and their choice of primary colour. It isn't intended for monochrome icon to be **required** to use adaptive icons. So specifying just the `background` and `foreground` attributes is suppose to continue to work as it did before, so I've marked this as a bug and will add this issue to a 12.0.1 milestone. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
