fix: add null checks in HtmlMovementMethod to prevent crashes #108
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.
Summary
Problem
The app was crashing with the following stack trace from Google Play Console:
Root Cause
At line 215, the code was comparing
currentImg.equals(imgs.get(i).getUrl())
without checking if:imgs
collection is nullcurrentImg
is nullimgs.get(i)
is nullimgs.get(i).getUrl()
returns nullAny of these being null would cause a NullPointerException.
Solution
Added defensive null checks:
imgs
andcurrentImg
are not null before iteratingTest Plan
🤖 Generated with Claude Code