There's a popover when I use https://developer.apple.com/documentation/corenfc to read the nfcTag, but I don't want that popover. Can I read the nfcTag without popover? I hope that there will be no pop-up window after enabling nfctag reading, and only start processing the obtained information when the correct nfcTag is read. I hope to realize that the user can perform other operations in the application and always open the nfcTag for reading before reading an nfcTag.Is it possible?How should I implement this function?
Search results for
nfc
1,176 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
According to the documentation, for app clips: If a user returns to a previously launched App Clip from the App Library or Spotlight, the App Clip uses the invocation URL that it previously used to launch the App Clip. Is there a way to see whether the invocation URL that is passed to the app is simply the cached URL from a e.g. Spotlight launch vs. whether it has actually come from an app clip invocation method like NFC/QR? Alternatively, is there a way to disable this caching altogether?
Hello, I need Near Field Communication (NFC) for one Project. The problem is that you need to enable NFC in Xcode Capabilities and need for that a Apple Developer Account. I tried to create a Apple Developer Account but because im 17 years old, im getting the error: Sorry, you can’t enroll at this time. Are there any solutions? Thanks for help!
Is it possible to write sequentially on multiple tags using NFC? e.g. I have 10 tags and in my app set the number of writing and pressing on a button start first writing on first tag. when wrote, start an other writting and so on....
Same issue. Can’t read any NFC enabled document anymore. Weird how can you break a functionality like this and not notice it at all.
Topic:
App & System Services
SubTopic:
General
Tags:
I figured this out. It was due to some third party software that I was using for talking with NFC. It expected me to keep a reference to its object.
Topic:
App & System Services
SubTopic:
General
Tags:
the same for me. don't work with nfc readers apps. If you try to use with the quick commands app and select NFC tag for action it read regular the tag and make the action. please help me because i use it for work.
Topic:
App & System Services
SubTopic:
General
Tags:
I am having a lot of trouble getting NFC to work a second time. The first time using it to read works just fine, but the second time I try it gives me errors about the delegate method not being found. The exact error is this: [CoreNFC] 00000002 8093c3f0 -[NFCTagReaderSession didDetectTags:connectedTagIndex:]:141 Delegate does not implement -tagReaderSession:didDetectTags: method I know that the delegate is set because it is calling the same code. I do invalidate the session after reading. I have stepped through the code and made sure that line is called. Does anyone have any suggestions?
I think I experienced the same. After updating to 15.4 I cannot read my nfc card. Anyone have solutions on this?
Topic:
App & System Services
SubTopic:
General
Tags:
Good afternoon, I have a problem with my iPhone 11 pro max, I have changed the charging connector and now it does not detect NFC, I have changed NFC too and it still does not pick up NFC, who can help me
Apple's docs for Background Tag Reading state clearly that: ...be aware there are times when the display is on and background tag reading is unavailable, such as if [...] Airplane mode is enabled. Is anyone aware of the actual reason behind this restriction? Consider these examples: User A visits a different country and doesn't have local cell service. They use WiFi to access the internet, but keep airplane mode on to avoid expensive roaming charges. They apparently need to pay roaming fees in order to scan an NFC tag. User B is actually on a plane (literally the reason for airplane mode). They strike up a conversation with their seatmate, who wants to share contact info using an NFC business card. It won't work until the flight lands. In both of these cases, airplane mode is restricting what seem to be harmless attempts to scan a tag. Further, users don't commonly understand this restriction, and I am at a loss for how to explain Apple's reasoning to frustrated customers. Does anyone have a
After updating to iOS 15.4 I can no longer read any NFC tags. I believe Apple Pay is working fine. Replication: Unlock iPhone, hold NFC tag to top back of phone (without case or other magnetic or metallic materials nearby). Default iOS behaviour should be to read the contents of a known working tag (works perfectly on an Android device) and display a popup to manage the tag information (e.g. Popup would ask permission to open Safari to open a web link programmed on a tag) 3rd Party Tools: Previous versions of iOS 15 beta allowed read and write of NFC tags using apps such as NFC and NFC Tools. I have used normal mode, compatibility mode, have attempted to (re)format the tag to no avail. When conducting a read or write using these tools a popup appears, but no tag can be read or written. Ready to Scan popup remains open. Further steps taken: Hard Reset: No effect
Do you need to be paying apple the 99$ a year for developing an app clip from a nfc or can you do this on a free account ?
Hi All, We are using a ST25DV NFC tag and Fast Transfer Mode. Our iOS app sends a custom command that sends some data as an input and expects a response from the tag that includes a payload of ~4000 bytes. We have successfully sent this command to the tag using the NFC Tap App on Android and received the full data response. However, on iOS (15.3.1-iPhone 12 Pro) as we loop through and get the response (256 bytes at a time), at random point during the reading of the response we get the following error: [CoreNFC] 00000002 80050360 -[NFCTagReaderSession transceive:tagUpdate:error:]:824 Error Domain=NFCError Code=102 Tag response error / no response UserInfo={NSLocalizedDescription=Tag response error / no response, NSUnderlyingError=0x283c3cde0 {Error Domain=nfcd Code=29 Tag Error UserInfo={NSLocalizedDescription=Tag Error, NSUnderlyingError=0x283c3c1b0 {Error Domain=com.apple.nfstack Code=20 No response from tag UserInfo={NSLocalizedDescription=No response from tag}}}}} We are not using .addres
+1 here. Bought NFC-Stickers, as I assumed that this is already working out. Disappointing experience. Had to google just to find out, that this isn't a build in feature
Topic:
App & System Services
SubTopic:
Core OS
Tags: