Nativization issues can be difficult to track down particularly for that reason.
I have one suggestion and one question:
- Try opening a copy of the project in 4.13, as there have been a few bugs fixed that may relate to this issue.
- Are you able to package the project successfully without Nativize Blueprint Assets enabled?
Also, if you take a look at your logs, you’ll see several divide by zero warnings, as well as other error messages that I’d like you to look into resolving as I continue to look into this.
Let me know the results of the 4.13 test, and if you are not able to package without Nativize Blueprints enabled please provide that output log as well.