Add a module dependency to NativizedAssets plugin

Is there a way of getting the blueprint nativization to add dependencies to other plugins? When I package my project in the 4.17 preview I get the warning

UATHelper: Packaging (Windows (32-bit)): UnrealBuildTool: Warning: Plugin 'NativizedAssets' does not list plugin 'CableComponent' as a dependency, but module 'NativizedAssets' depends on 'CableComponent'.

Looking at BaseEditor.ini it looks like there’s a “AdditionalPublicDependencyModuleNames” array I can add values to but adding +AdditionalPublicDependencyModuleNames=CableComponent to my BlueprintNativizationSettings in DefaultEditor.ini doesn’t fix the warning. Since it’s a warning it doesn’t prevent packaging but I’d prefer to fix any warnings if at all possible.

i have the same warning with Paper 2D in 4.17.0:

“Warning: Plugin ‘NativizedAssets’ does not list plugin ‘Paper2D’ as a dependency, but module ‘NativizedAssets’ depends on ‘Paper2D’.”

it’s the only warning i get and my game crashes on android when i try to Nativize.

Have you figured it out eventually? Even though it’s just a warning, it actually prevents my project from building later on.

Hey CodeSpartan, Noticing this issue myself as well (with the dialogue plugin). How are you noticing it preventing building? I have 3 different plugins that warn on this but am able to make fully nativized shipping builds.

You have to add plugin dependencies to your MyProject.uplugin file now, at the bottom under the Modules section. Here’s a link where it’s discussed:

NativizedAssets is a plugin generated from blueprint nativisation for packaging purpaces. Blueprint Nativisation should add plugin dependency same way as it does with module, so it is a bug in Blueprint Nativisation that causing this warning and it a risk for potential packaging errors. I meet another user on discord that have this issue and point me to this post. So i move this to Bug Raport.

Warning it self in this case can be ignored as long as proper plugin is packaged

Has this been fixed?

Not so far (in 4.18.1) and I’ve never even gotten an official response acknowledging that they’re aware of the problem, either here or in the forums when I asked about it during the 4.18 preview.

Yeah they do that unless you can reproduce it (less work for them I guess?)

It seems this is no longer happening in 4.19 so I’m marking the question as answered.

I think it might be this one:

Im getting the issue in 4.18, will update this once 4.19 is final and i have tested that…