You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
encodeToData and decodeFromData are not symmetrical, according to the documentation. That said, perhaps we can find some other way of serializing/deserializing this information if you need to store it locally.
The encodeToData returns this 3 byte (hex) byte sequence for file 01: 0000e0
As per NTAG424 datasheet the "GetFileSettings" command should return a minimum of 7 bytes + extra bytes if SDM is enabled:
If I'm using the (hex) byte sequence "0000e012200000" as input for decodeFromData I can build a new FileSettings object. I didn't test for decoding data including SDM options.
Running FileSettings.encodeToData() is giving to few data, e.g.
File 01: length: 3 data: 0000e0
Using this output as input for FileSettings.decodeFromData(xx) gives an ArrayIndexOutOfBoundsException:
NTAG 424 DNA NT4H2421Gx.pdf page 69 ff is stating a minimum of 7 bytes + extra bytes if SDM is enabled.
Greetings
Michael (AndroidCrypto)
The text was updated successfully, but these errors were encountered: