Using the Nativize Blueprint Assets option can cause the extents of a collision component defined in code and inherited by blueprints to use its default values in a packaged build instead of the extents defined in the blueprint. This also occurs even if no extents are being explicitly defined in the constructor.
Regression?: No
This also occurred in 4.13
Head over to the existing Questions & Answers thread and let us know what's up.