feat: fix old listener destroy but not remove lead to new same app ur… #14669
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
When url A and B mapping to appA in mapping cache file, but A is mapping to appA and appB in remote.
A subscribe first, put appA instance listener. but onEvent change to appA and appB mapping.
Then destroy appA instance listener, but not remove.
And then B subscribe, on account of old instance listener not remove, it's subscribe failed.
Brief changelog
Verifying this change
Checklist