Fixed: Unable to discover M2 Reader #3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is already fixed on version 1.2.0. Thank you for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Was also encountering some issue when discovering M2 Card Readers.
Going through the code, native code was actually able to discover the M2 Card Reader.
It seems that it was failing when parsing the json to
StripeReaderobject.When discovering an M2 Card reader, it was not having any
originalJSONfield which was causing it to fail.e.g
Sample json object received when an M2 reader is discovered (I've only changed the serial number):
{locationStatus: 2, deviceType: 3, originalJSON: null, serialNumber: <SERIAL_NO>, batteryStatus: 0, locationId: null, simulated: false, availableUpdate: false, label: null}]Added some null check into the field for it to not cause error.