-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(core): inject APP_ID before injector is destroyed
#61885
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
Conversation
|
Are you sure the application injector can be destroyed at this point ? |
|
Yes, I have an app which reproduces this issue. |
|
can we try to capture that in a test then ? |
|
yes, it's reproducible in existing tests in the repo, it didn't capture before because its wrapped with |
In this commit, we request `APP_ID` outside the `onDestroy` callback because the injector might already be in a destroyed state when the callback runs.
c511f0a to
6fead75
Compare
|
Caretaker note: the presubmit is "green", this PR is ready for merge. |
|
This PR was merged into the repository by commit 31da435. The changes were merged into the following branches: main, 20.0.x |
In this commit, we request `APP_ID` outside the `onDestroy` callback because the injector might already be in a destroyed state when the callback runs. PR Close #61885
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In this commit, we request
APP_IDoutside theonDestroycallback because the injector might already be in a destroyed state when the callback runs.