G'day. At my office the doors are locked with an NFC reader. We carry around a little NFC tag on our key chains which will read out a number and this then will open the door if the number matches a number in the database. I am tired of carrying around the tag, people keep loosing it, forgetting it and it would be nice to open the door using a Phone - which we tend to always have on us. So I used a credit card which is NFC enabled to readout the NFC information, added this number to the database and can now open doors using my credit card. This is pretty cool. If I forget my keys (most likely they will be on the desk but silly me left the desk without them), I may have my wallet with me. Then I tried Wallet.app on my iPhone and select the same credit card. However the door doesn't open. When looking in the door software I noticed that the tags will always transmit the same number. So does my credit card. However Wallet.app will read out 4 readings (or maybe just one very lon
Search results for
nfc
1,176 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Make sure that you have NFC on, which is obvious but may not be on. Then, may I ask how you are trying to unlock the door. If you are not, I think that you should try double-clicking the side button like when you would do it by an NFC cash register, as that would transmit NFC data.
Topic:
App & System Services
SubTopic:
Hardware
Tags:
Hi Guys, we have the same issue and recognized that is depend on URL/Weblink on NFC chip, but i make NO SENSE. for example following Weburls works fine: tapped.to tapped.to/ tapped.to/page tapped.to/page/xyz tapBed.to/pages But if we add: tapped.to/pages tapped.to/pages/xyz than we got the error CPSErrorDomain-Error 2 we also tried (with tld .de) tapped.de/pages or w.tapped.to/pages (Subdomain, www. to) what works fine.... It makes no sense? Or apple blocked our domain? Btw. this happen only with background scanning on iOS 14.1 (iphone 12 pro ) and ios 14.4 (18D5030e) (iphone 11 pro) with iphone X 14.1 (18A395) native NFC Scanner it works fine.
Topic:
App & System Services
SubTopic:
General
Tags:
Hi Guys, we have the same issue and recognized that is depend on URL/Weblink on NFC chip, but i make NO SENSE. for example following Weburls works fine: xyz.tld xyz.tld/ xyz.tld/page xyz.tld/page/xyz xZz.tld/pages But if we add: xyz.tld/pages xyz.tld/pages/xyz than we got the error CPSErrorDomain-Error 2 we also tried (with tld .de) xyz.tld/pages or x.xyz.tld/pages (Subdomain, www. to) what works fine.... It makes no sense? Or apple blocked our domain? Btw. this happen only with background scanning on iOS 14.1 (iphone 12 pro ) and ios 14.4 (18D5030e) (iphone 11 pro) with iphone X 14.1 (18A395) native NFC Scanner it works fine.
Topic:
App & System Services
SubTopic:
General
Tags:
FYI App Clips Resolved in iOS & iPadOS 14.4 Beta In addition to using Code Scanner, you can now launch a local experience via Camera, NFC, Safari Smart App Banner, or iMessage. (68962905) Local Experience instructions: https://developer.apple.com/documentation/app_clips/testing_your_app_clip_s_launch_experience
Topic:
App & System Services
SubTopic:
General
Tags:
FYI App Clips Resolved in iOS & iPadOS 14.4 Beta In addition to using Code Scanner, you can now launch a local experience via Camera, NFC, Safari Smart App Banner, or iMessage. (68962905)
Topic:
App & System Services
SubTopic:
General
Tags:
Hi Guys, if we use our NFC Chip (Background Scanning) with our domain xyz.tld/pages (NFC with URL) than we get following Error: CPSErrorDomain error 2. If we use other URL, than it's works fine, for example, following URLS works fine: xyz.tld xyz.tld/ xyz.tld/page xyz.tld/page/xyz xZz.tld/pages But if we add: xyz.tld/pages xyz.tld/pages/xyz than we got the error CPSErrorDomain-Error 2 we also tried (with different tld) xyz.tlx/pages or x.xyz.tlx/pages (Subdomain, www. to) what works fine.... It makes no sense? Or apple blocked our domain? Scanning with Iphone X or other normal NFC Reader are not a problem and works fine, only Background scanning have this issue. This happen only with background scanning on iOS 14.1 (iphone 12 pro ) and ios 14.4 (18D5030e) (iphone 11 pro) with iphone X 14.1 (18A395) native NFC Scanner it works fine.
I'm only able to write to NFC a URL with https. So it's https://xyz. tld ... Why this error happen? Maybe because we using stripe? We tried to integrate Apple Pay for payments on this webpages, but because we have some issues we removed this payment method and of course we deleted the domain for verfication. Everything looks clear. We have no really idea why this page get this Error and no idea what kind of error it is? If you want, you can try by self: tapped.to/pages If you add this to NFC and try background scanning it will fail.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I would like to know if it is possible to read/write on tag that are not formatted NFCForum (Ndef). I am especially concern with ISO 15693 tag. NFC Core with NFCISO15693Tag seems to be capable of iy but I couldn't find on the store any application that can do it (with new iphone SE 2020 and iOS14.1)
hello! The same question to Apple company. 21 century and we can not use NFC on the full power. Normally just one solve - add transport card to wallet and use ID of this card in your base. Transport card have static ID.
Topic:
App & System Services
SubTopic:
Hardware
Tags:
Hi Team, I am unable to generate certificates anymore as i have reached the maximum limit for pass type ID with NFC certificates. Can you please help to increase the limit to 100? My project needs to generate these certificates. Thanks, Sanga Mithra.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
WWDC20
Signing Certificates
Wallet
Developer Program
I created a demo to test core NFC and failed to write the iso15693 tag. Byte bytes[8]={0x12,0x21,0x04,0x74,0x65,0x73,0x74,0x00};t NSData *data = [[NSData alloc] initWithBytes:bytes length:8]; [iso15693Tag writeSingleBlockWithRequestFlags:RequestFlagSelect blockNumber:0x04 dataBlock:data completionHandler:^(NSError * _Nullable error) { t if (error) {t tt NSLog(@Failed to write tag!); tt} else { tt NSLog(@write succeeded!); tt } t }]; I couldn't execute successfully and got the error message: Error Domain=NFCError Code=100 Tag connection lost UserInfo={NSLocalizedDescription=Tag connection lost} I would like to ask if core NFC supports writing iso15693tag? I think I need a successful example of how to create a correct blockdata. I hope someone can help me. Thank you very much!
I have the same issue, but we're only using https:// as a prefix so the suggested solution is not working. Strangely there is no sensible pattern when it works and when it doesn't work. Example: ourdomain.com/profile/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 <-- does not work ourdomain.com/profil/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 <-- works By just changing profile to profil the iPhone will scan the nfc properly. When there is profile in the url, iOS seems to think this involves an AppClip. It doesn't stop there. This is also strange: When I make a QR code from the link ourdomain.com/profile/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 this happens: Scan the QR code in the camera App -> it works!!! Scan the QR opened from the control center -> Same problem as with NFC!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
This problem seems to be duplicated and on one tread it's marked as solved, but it's not. So I add some more information here: I have the same issue. Strangely there is no sensible pattern when it works and when it doesn't work. Example: ourdomain.com/profile/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 <-- does not work ourdomain.com/profil/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 <-- works By just changing profile to profil the iPhone will scan the NFC properly. When there is profile in the url, iOS seems to think this involves an AppClip. It doesn't stop there. This is also strange: When I make a QR code from the link ourdomain.com/profile/n/6d18aadb-dfcc-47df-a9ac-d30b2cbad9c2 this happens: Scan the QR code in the camera App -> it works!!! Scan the QR opened from the control center -> Same problem as with NFC!
Topic:
App & System Services
SubTopic:
General
Tags:
I'm trying to implement an app with NFC. I have to connect to MIfare tag. I'm notified in tagReaderSection function and the field tags contains a tag, but the value of this tag is [0] = (NFCTag) (0x40) Printing description of ((CoreNFC.NFCTag) (0x40)): ▿ NFCTag t- miFare : (lldb) and im not able to connect to it. In the info file I have add the string: com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 nfcTagReaderSession = NFCTagReaderSession(pollingOption: [.iso14443], delegate: self) tttt tttnfcTagReaderSession?.begin() tfunc tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { ttt tttt ttttif case let NFCTag.miFare(tag) = tags.first! { ttttttnfcTagReaderSession?.connect(to: tags.first!) ttttttttttt { What am I doing wrong?? thanks for the support PS: the NFC chip is Mifare Ultralight version 2 productType Ntag(04) [Xcode 12.0, IOS 13.0]