issue/3154-login-site-address-crash-fix #3203
Merged
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.
Fixes #3154 by adding a null check when user enters a site address during login. I haven't been able to reproduce the issue but it looks like we set the
mSiteAddressInput=null
when the fragment is destroyed. So if theonTextChanged
is called before themSiteAddressInput
could be initialised again, this crash could potentially happen.Given that we needn't update the
mSiteAddressInput
field after the fragment is destroyed, it seemed enough to do just a null check here to ensure that this crash doesn't happen again.Update release notes:
RELEASE-NOTES.txt
if necessary.