Posts

Post not yet marked as solved
2 Replies
1.9k Views
Description:We are using the `read NFC tag in background` functionality but we are also reading the tags in foreground mode.If we do the Tag scan with NFC, having the app opened (in foreground), we also receive the notification about the scan result comming from the background read functionality. In result, we are experiencing the Tag read completion twice at once being in foreground mode: from foreground read and the background listener.Step-by-step instructions:1. Setup the `NFC background read` listener and the `NFC foreground read` functionality2. Open the app3. Run the NFC session4. Move the iPhone towards the Tag to read itResults we see:The Tag is being read but we are also receiving the notification from the `background NFC reader` at the same time.Results we expect:If the user is in the foreground mode, the app is opened, and he reads the tag, we expect not to receive the notification from the background NFC listener. The notification from the background NFC reader should come only when the app is not active.Suggestions / additional questions1. Is there any way to disable the backgeound NFC reader from notifying when the app is in foreground?2. Let the developer to control the time of closing the foreground NFC session / blocking the bacgound NFC reader from notifying3. Possibility to enable the background NFC reader when the Tag is no longer in iPhones read range
Posted
by keisyrzk.
Last updated
.
Post not yet marked as solved
0 Replies
424 Views
Hi,we have a specific need to listen to CoreLocation's didRangingBeacons and for the NFC tag simultaneously.Logic description:- we are listening to the didRangingBeacons- we have specified a RSSI treshold for the beacon and for running a NFC session- when the RSSI is reached for the NFC we show its popup but still listening to didRangingBeacons in case of we catch earlier beacon communication rather than via NFC with the tag - to conclude, we are open for both Beacons and NFC simultaneously and want to catch whichever of them which will communicate earlier with the phonecase 1If we fire the NFC session we are still listening to didRangingBeacons. If we catch communication with a beacon before the tag via the NFC then we continue with the beacon and invalidate the NFC sessioncase 2If we catch the communication with the beacon then we do not run the NFC session at all.The problemFrom time to time, the NFC is going to be broken after the identification with beacon/NFC in the situation described above. By broken I mean the NFC popup does not show up in our app but also in other apps. I have investigated the problem and from the code side it looks like the NFC session is invalidating properly and also starting properly but there is no popup anymore.The only solution in this case is the iPhone reboot.Does anyone know why is that happening and how to solve this problem? This only happens in collaboration with CoreLocation didRangingBeacons.Many thanks.
Posted
by keisyrzk.
Last updated
.