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
When scanning an NFC Tag, the message "Stack Error" sometimes appears. This is not so nice for the user and he also cannot do anything with the error message. I would like to suppress this message. If the NFC Tag could not be scanned, just keep scanning until it could read the NFC tag (without stack error message). Is there any way?
Steps to Reproduce
Hold the NFC tag very briefly against the iPhone and pull it away again directly.
Expected Behavior
Actual Behavior
Basic Information
Version with issue: all
Last known good version: never
IDE: -
Platform Target Frameworks:
iOS: 13 - 16
Nuget Packages: current
Affected Devices: iPhones
Screenshots
Reproduction Link
The text was updated successfully, but these errors were encountered:
Other error messages also occur. This happens predominantly when the NFC chip could not be scanned correctly, e.g. when there is a lot of distance. After the error message has occurred, the NFC scan is always aborted.
I would like to suppress the error message and continue scanning via NFC. I have looked at the source code and found the appropriate places. I think if this make configurable weather error messages should be suppressed or not, it will remain backward compatible.
Since the last commit for was over a year, here now the question whether the project is dead? If not, I would consider creating a PullRequest if it would be accepted in a timely manner.
Description
When scanning an NFC Tag, the message "Stack Error" sometimes appears. This is not so nice for the user and he also cannot do anything with the error message. I would like to suppress this message. If the NFC Tag could not be scanned, just keep scanning until it could read the NFC tag (without stack error message). Is there any way?
Steps to Reproduce
Hold the NFC tag very briefly against the iPhone and pull it away again directly.
Expected Behavior
Actual Behavior
Basic Information
Screenshots
Reproduction Link
The text was updated successfully, but these errors were encountered: