Fixed error when reading an iso15693 nfc tag with no blocks #3229
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.
Fixed a zero allocation error when reading an iso15693 nfc tag with no additional blocks.
What's new
When reading an iso15693 nfc tag that reports zero blocks, do not try to allocate memory for reading or try to read the inexistent blocks. This works around a hard crash of the flipper when reading e.g. a FreeStyle Libre 3 tag.
Verification
Try to read an iso15693 nfc tag that just has an UID but no additional data. The flipper should not crash. Previously it crashed when trying to allocate 0 bytes through
malloc
insimple_array_init
.Checklist (For Reviewer)