diff options
| author | Jan Moeller <[email protected]> | 2025-04-30 09:17:16 +0200 |
|---|---|---|
| committer | Jan Moeller <[email protected]> | 2025-06-10 16:04:02 +0200 |
| commit | 7d2ac27c1844cfd954827771f2aa8013c9e9f4a7 (patch) | |
| tree | 98d54fb64cf3726098251a487778eace48681ad0 /src/bluetooth/android/androidbroadcastreceiver_p.h | |
| parent | 227718d5a7e5902d1935d7a05c56ef87eae3c360 (diff) | |
The call to getMaxTransceiveLength() and isConnected() might fail if
the card was lost in the meantime. Especially Samsung smartphones seem
to not communicate the loss right away.
Consequently a Java exception is thrown:
java.lang.SecurityException: Permission Denial: Tag ( ID: 08 B1 F8 BA ) is out of date
at android.nfc.Tag.getTagService(Tag.java:382)
at android.nfc.tech.BasicTagTechnology.getMaxTransceiveLengthInternal(BasicTagTechnology.java:138)
at android.nfc.tech.IsoDep.getMaxTransceiveLength(IsoDep.java:183)
Permission Denial: Tag ( ID: 08 B1 F8 BA ) is out of date
at android.nfc.Tag.getTagService(Tag.java:382)
at android.nfc.tech.BasicTagTechnology.isConnected(BasicTagTechnology.java:63)
at android.nfc.tech.IsoDep.isConnected(IsoDep.java:40)
If this occurs, it seems safe to assume that the card is gone and the
corresponding error and targetLost should be reported.
Fixes: QTBUG-136506
Pick-to: 6.10 6.9
Change-Id: Ie6432aa9a1e4136f96463311312a1a065484111e
Reviewed-by: Assam Boudjelthia <[email protected]>
Reviewed-by: Ivan Solovev <[email protected]>
Diffstat (limited to 'src/bluetooth/android/androidbroadcastreceiver_p.h')
0 files changed, 0 insertions, 0 deletions