goffioul commented on issue #1468: URL: https://github.com/apache/cordova-android/issues/1468#issuecomment-1198405448
> The legacy system as already explained above is incompatible with the Android's splashscreen API. The best this can reach us is having 2 splashscreens (one from native android which will be unavoidable, and the one from the old cordova splashscreen plugin) where you can only control the splashscreen plugin's splashscreen. An example of this could be seen if you ran a cordova-android@10 app on an Android 12 device/emulator. > > The splashscreen plugin has been updated to not install on cordova-android@11, because they both clobbers the same namespaces and cause conflicts. Some preferences are reused, but outside of that, if similar behaviour is wanted, I suppose a workaround is to fork the splashscreen plugin, and change the namespaces / JS clobber points so that you have access to both cordova-android@11 splashscreen APIs as well as the legacy splashscreen APIs. But I don't see this being a supported feature at an Apache level. Thanks for the extensive response. We can just agree to disagree, but I wouldn't say the legacy system is incompatible with the Android 12 spashscreen API. It could be seen as complementary. Given the limitation of that new API, I would have prefered to see cordova-android embracing the new API as a separate feature, instead of clobbering the existing legacy system and making it completely incompatible. I don't see the potential double splashscreen as a serious/blocking issue. This would have been less disruptive for app developers. > Regarding splashscreen drawing issues, there is are bugs in the android emulator surrounding drawing the splashscreen. It's noted in our [documentation](https://cordova.apache.org/docs/en/11.x/core/features/splashscreen/index.html#android). The problem I see is different than the one described in the doc. But it may still be a bug in the emulator, though. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
