-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[0.63] Fix native modules not being re-initialized on reload (#6159) #6176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.63] Fix native modules not being re-initialized on reload (#6159) #6176
Conversation
cc @vmoroz, @acoates-ms |
9a08fd3
to
811a5d6
Compare
Looks like this code is already in master and this is the port to 0.63. Adding the appropriate tag for triage. |
586fa80
to
073f378
Compare
When calling `ReactNativeHost::ReloadInstance()`, `ReactPackageProvider`s are not reiterated and thus not calling `AddAttributedModules()`. As a consequence, the native modules that were loaded the first time the app was loaded, no longer "exist" after a reload.
073f378
to
e7b9341
Compare
@acoates-ms, @NickGerleman, @vmoroz: Could you please take another look? Finally got all the checks to pass. |
@acoates-ms you were of the opinion this one was severe enough to be backported, right? @chrisglein @asklar @kmelmon @Khalef1 any concerns backporting this? |
No concerns on my side for backporting |
Yes we should take this. |
Hello @NickGerleman! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
When calling
ReactNativeHost::ReloadInstance()
,ReactPackageProvider
s are not reiterated and thus not callingAddAttributedModules()
. As a consequence, the native modules that were loaded the first time the app was loaded, no longer "exist" after a reload.Microsoft Reviewers: Open in CodeFlow