Framework might call scheduleForcedFrame when the engine is in pause or detached state. In this case, engine will drop the schedule frame request without calling back framework to draw the rendering tree. This become problematic because framework is waiting frame to be scheduled and blocking any future schedule frame which results in no future frame will ever be drawn.

One use case is rotating screen when app is in the background. Framework will like to update the rendering tree before the app is actually brought into the front.

Currently, we work around this issue by adding a check in scheduleforcedframe to abort if the frame is not enabled which makes it essentially the same as scheduleframe.