All Collections
FAQ's
NFC Check-In Error Messages
NFC Check-In Error Messages

What they mean and how you can resolve them

Martin Callan avatar
Written by Martin Callan
Updated over a week ago

Some of the error messages are quite specific and the reason is very clear. Others are environmental errors, so maybe user error, network related or Tag Installation related.

Error Message: That's not right! We could not detect the freshOps Tag

Reason: NFC is on but the NFC Reader does not pickup a NFC Tag.

Possible Fix: Ensure you know where on your Device the NFC Reader is located. It isn't always in the middle on the back for Android Devices. Search Google for your specific device. Apple Device NFC Readers are in the very top of the phone. When you press Check-In, Tap the tag promptly, don't take too long as it'll time out.

Error Message: Oops! That's not right, please use the correct site freshOps tag.

Reason: A freshOps Tag has been detected, but it isn't the Tag allocated to this specific site.

Possible Fix: Contact your Employer and confirm the tag ID allocated to site matches the tag ID on the tag you are trying to TAP

Error Message: Oops! You are using an unsupported NFC tag. Please use the correct freshOps tag.

Reason: Unsupported/Non- freshOps NFC Tag is being identified by the freshOps NFC Reader.

Error Message: We could not read the data in the tag. Please contact freshOps Technical Support through the Menu.

Reason: Unable to read data from the tag (unsupported data type used). NFC Tag was read, but the data on it was incorrect. Could be interference occurring with NFC Field.

Possible Fix: Check that there is no metallic object interfering with the NFC. Metal behind and around the NFC Tag. Metal within Phone Cases. Phone Rings Etc.

Error Message: There is no data in the tag. Please contact the freshOps Technical Support through the Menu.

Reason: No data available in tag. Maybe a faulty freshOps Tag

Error Message: That's not right! We could not detect the freshOps tag. Please contact the freshOps Technical Support through the menu.

Reason: User scans the correct tag, but for some technical, environmental or physical reason it is not detecting the data.

Did this answer your question?