Skip to content

Conversation

@markdevocht
Copy link
Contributor

The fix's logic is what @gosha212 came up with and is a solid idea.

First of all,
the problem:
During the Reload, some of the surfaces were still being destroyed at a stage that the EventEmitter had already changed to a different instance.
This caused the crash because the previous EventEmitter instance's _callableJSModules object no longer existed (nil) and caused an Assert to throw an exception.

The fix:
After spending a lot of time going through the code and getting to know the code we came a couple of times close the a solution but not something that would be clean or right enough, UNTIL... @gosha212 came up with an idea to generalize the fetching of the right EventEmitter object only at the time it was actually needed.

gosha212
gosha212 previously approved these changes May 29, 2025
@gosha212 gosha212 marked this pull request as ready for review May 29, 2025 13:00
@markdevocht markdevocht enabled auto-merge (squash) June 4, 2025 07:57
@markdevocht markdevocht merged commit 8a9638f into master Jun 4, 2025
4 checks passed
@gosha212 gosha212 deleted the bugfix/rn77-Reload-crash branch June 4, 2025 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants