I have a bizarre scenario for which I cannot seem to figure out the cause. An issue was reported to us by one of our clients where their tags were not being read properly. It was quite bad for the whole day where most tag scans were not being read properly. The occurrence of this issue has reduced and now it occurs intermittently. Because of that, it’s a bit hard to reproduce it at will (since I don’t know what was causing it in the first place). The only way I was able to reproduce it (by accident) was to take the reader about 10 meters away from the iPad it was connected to and surrounded it by bluetooth devices.Please note that this was only for testing purposes. The actual setup where this issue occurred is quite the opposite where the reader is right next to the iPad it is connected to

For my testing purposes, I logged the uuid, attr, and error (if available) in addition to the logs generated by the SDK. With my testing, the tag was mostly read properly and sometimes, the uuid would return a value of 63 00 along with an error (as you can see in the logs below). Then finally, the issue occurred (I’ve made it bold in the logs for clarification). If you look closely, the normal uuid for this tag is 04 72 B5 D2 90 49 81 but in this instance, it came back with 04 72 B5 which is the first half of the actual uuid. I’m not entirely sure what would cause the device to return only a partial uuid.