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
We got direct feedback from 3 companies that use the Reader API on ticket terminals and who have encountered the same issue with the reader.ObservableCardReader interface: the absence of the ability to set a time limit for card insertion detection.
Currently, the startCardDetection method can initiate a detection without a time limit, which means that terminals that need to limit the duration of a detection attempt have to manage this limit by adding a dedicated overlayer on top of the Reader API.
In some embedded devices, to save electrical energy, the reader solutions do not natively offer the possibility of detecting an insertion over an indefinite period (this is the case, for example, with the IOS NFC API).
→ we therefore plan to add a parameter to limit the detection time of a card insertion in a future Reader API evolution.
The text was updated successfully, but these errors were encountered:
We got direct feedback from 3 companies that use the Reader API on ticket terminals and who have encountered the same issue with the reader.ObservableCardReader interface: the absence of the ability to set a time limit for card insertion detection.
Currently, the startCardDetection method can initiate a detection without a time limit, which means that terminals that need to limit the duration of a detection attempt have to manage this limit by adding a dedicated overlayer on top of the Reader API.
In some embedded devices, to save electrical energy, the reader solutions do not natively offer the possibility of detecting an insertion over an indefinite period (this is the case, for example, with the IOS NFC API).
→ we therefore plan to add a parameter to limit the detection time of a card insertion in a future Reader API evolution.
The text was updated successfully, but these errors were encountered: