Description

Packaging a project that includes a precompiled plugin fails with an error that an object reference is not set to an instance of an object.

This only happens in the Binary Engine. If the Engine is built from source code, the package process completes successfully.

REGRESSION:
No. It was not possible to create a precompiled plugin in 4.19.

Steps to Reproduce
  1. Create a new Basic Code project.
  2. Build the project in Visual Studio.
  3. Run the project with Visual Studio's debugger.
  4. Add a new Blank plugin to the project.
  5. In the new plugin's .uplugin file, change the plugin type from Developer to Runtime.
  6. In the plugin's Build.cs file, add the following line: bPrecompile = true;
  7. Build the project for Development Editor, Development, and Shipping.
  8. Copy the plugin into the Engine's Plugins directory (in my test I copied it into Plugins/Runtime).
  9. Create a new Blank Blueprint project.
  10. Enable the plugin that was copied into the Engine in the new project.
  11. Package the project for Development Win64.

RESULT:
The package process fails with the following error: ERROR: System.NullReferenceException: Object reference not set to an instance of an object.

EXPECTED:
The project packages successfully with the plugin included.

Have Comments or More Details?

There's no existing public thread on this issue, so head over toAnswerHub just mention UE-64986 in the post.

0
Login to Vote

Non-Issue
ComponentDevTools
Affects Versions4.224.20.3
CreatedOct 9, 2018
ResolvedOct 9, 2018
UpdatedOct 9, 2018