Comments on: #53 First steps with NFC on iOS 13

By: Puneet

Tue, 10 Dec 2019 15:56:09 +0000

I am getting an error “tagReaderSession:didInvalidateWithError – Error Domain=NFCError Code=201 “Session timeout” UserInfo={NSLocalizedDescription=Session timeout}”. The method
func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) {
is not calling. How can I fix that?

]]>

By: Luciano Nascimento

Sat, 14 Sep 2019 14:40:50 +0000

Amazing this post! It help me a lot, because I’m developing a app for a company of transport in my city, and just iPhone we are with problem to implementing, but now I will be able to finish them. Thank you so much!

]]>

By: Mark

Thu, 01 Aug 2019 15:17:34 +0000

What “standard” did you settle on for your exploration? I’d like to buy some NFC badges to read and write but there’s a ton out there and I’m assuming some are easier than others.

]]>

By: Babidi

Sun, 28 Jul 2019 01:23:54 +0000

Did writing tags work for you? For me it fails with a not connected error (after saying it is writable and connected)…

]]>

By: ck

Wed, 24 Jul 2019 15:25:01 +0000

Xcode 11 beta 4
‘wellKnowTypeTextPayload(string:locale:)’ was deprecated in iOS 13.0

Do you know how to fix ?

]]>

By: Richie

Sun, 21 Jul 2019 03:23:42 +0000

Hey – when I try this with a NTAG215, it fails in the tag.writeNDEF(myMessage) completion with a Tag is not connected error – any ideas why this might be? (on ios13 beta 4)

]]>

By: rldaulton@gmail.com

Thu, 18 Jul 2019 18:13:12 +0000

So…although the changes mean that select devices can write directly to tag, would this theoretically mean that a device itself could also emit a NFCNDEFMessage as a readable signal to another device?

For example, the device itself could act as “the tag”, in a way. And another device, when in proximity, could detect, retrieve, and read the NDEF message from the device of origin?

]]>

By: Ryan

Thu, 18 Jul 2019 18:08:40 +0000

For example, the device itself could act as “the tag”, in a way. And another device, when in proximity, could detect, retrieve, and read the NDEF message from the device of origin?

]]>