As the title suggests OnApplicationStart can run too Early on some Mono Games.
This causes unintended behavior for things like GameObjects when instantiated from OnApplicationStart.
Resulting in it ignoring DontDestroyOnLoad or hideFlags, hideFlags causing components not to run, the GameObject getting destroyed on first Scene Load, etc.

Cant this simply be fixed by invoking the callback when MLs component receives the Start message?

Cant this simply be fixed by invoking the callback when MLs component receives the Start message?

Possibly not entirely sure.

Cant this simply be fixed by invoking the callback when MLs component receives the Start message?

Possibly not entirely sure.

When is it called atm?

Cant this simply be fixed by invoking the callback when MLs component receives the Start message?

Possibly not entirely sure.

When is it called atm?

Inside Core’s Start which gets called by a runtime invoke hook
Delaying it a little more using the component might be viable

Cant this simply be fixed by invoking the callback when MLs component receives the Start message?

Possibly not entirely sure.

When is it called atm?

Inside Core’s Start which gets called by a runtime invoke hook Delaying it a little more using the component might be viable

imo OnApplicationStart should become obsolete and OnStart should be added

OnApplicationLateStart is now be running from the Support Module Component's OnStart method.