breautek commented on issue #1461: URL: https://github.com/apache/cordova-android/issues/1461#issuecomment-1192556052
> Is there a rough "release date" for this new plugin? [email protected] is and has been released. It's been updated so it doesn't install on cordova-android@11 so it doesn't cause conflicts, particularly if you still require it because you develop for other platforms. > At least provide SOME lead as to which setting is valid in the NEW Android-11 version and which ones do no longer apply. I think Erisu clearly stated what is new and valid for cordova-android@11 moving forward is [documented](https://cordova.apache.org/docs/en/11.x/core/features/splashscreen/index.html). And like he mentioned, some preferences when applicable, was carried over from the older splashscreen plugin, which are also documented. > The prepare stage should not throw a null pointer -- it's that simple. It's a bug This is a nature of any plugin system. Yes it's an issue but not necessarily within Cordova codebase. From what I understand reading this thread, there are two occurrences where this happens. 1. > In our case, this issue was resolved by either omitting the line `<resource-file src="icons/android/adaptive/bgcolor.xml" target="/app/src/main/res/values/colors.xml"/>`. If you're manually managing/overriding the colors.xml` file which the core platform now depends on. Then you'll need t re-implement everything that Cordova does to manage this file to support all the features that Cordova has around this file. This isn't a bug with Cordova. 2. > An interesting thing is however happening when the Android platform is added with our config.xml file, perhaps because we use the plugin [email protected] with its plugins\cordova-plugin-firebasex\src\android\src\android\colors.xml It is possible that plugins have defined their own colors.xml because they have their own native UIs. If they are overwriting Cordova's colors.xml, that will make plugins incompatible with cordova-android@11. They'll have to be updated to use [<config-file](https://cordova.apache.org/docs/en/11.x/plugin_ref/spec.html#config-file) to append to the file, or [<edit-config>](https://cordova.apache.org/docs/en/11.x/plugin_ref/spec.html#edit-config) if they require to edit an existing node. As with all major releases, there is potential for breaking changes. In this specific case there is incompatibility with cordova-android@11 and firebasex due to a configuration conflict. But this doesn't make it a bug. I would suggest to raise an issue against firebasex maintainers if there isn't one already to let them know that there is a configuration conflict. -- 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]
