Fixing fb4a crashes due to null pointer exception (#55529)

Summary:
[Android][Fixed] - Fix null pointer crash in FabricUIManagerBinding::driveCxxAnimations by adding null check for scheduler

Pull Request resolved: https://github.com/facebook/react-native/pull/55529

Crash failures during e2e: https://www.internalfb.com/intern/test/562949977559616
logview: https://fburl.com/logview/65na7gyr

Reason: null dereference
Pull Request resolved: https://github.com/facebook/react-native/pull/55529

Crash failures during e2e: https://www.internalfb.com/intern/test/562949977559616
logview: https://fburl.com/logview/65na7gyr

Reason: null dereference

Reviewed By: javache

Differential Revision: D92986523

fbshipit-source-id: 2a193cdc93a44a59fedfb7974bb694546a2000f6
This commit is contained in:
Dileep Siva Sai Nallabothu authored and meta-codesync[bot] committed 2026-02-12 16:09:33 -08:00
1 parent d7a1d080c2
commit 349cf1595b
1 file changed
+7 -1
@@ -52,7 +52,13 @@ void FabricUIManagerBinding::setPixelDensity(float pointScaleFactor) {
}
void FabricUIManagerBinding::driveCxxAnimations() {
getScheduler()->animationTick();
auto scheduler = getScheduler();
if (!scheduler) {
LOG(ERROR)
<< "FabricUIManagerBinding::driveCxxAnimations: scheduler disappeared";
return;
}
scheduler->animationTick();
}
void FabricUIManagerBinding::driveAnimationBackend(jdouble frameTimeMs) {