Hello, I have ICode Slix and Slix 2 NFC tags. I'm working on an iOS app for reading and writing data to these tags. I've tried various approaches, but I'm having trouble with the writing part. Could you please assist me in understanding how to write encode URL in that tags Here's my current code Because these tag is not bydefault NDEF format and I want to right url in that tag and make it NDEF formattable. I tried to write data with NFC Tool application it can write data easily in that but my code doesn't work. how to right data in NFC forum type 5 tags? func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { print(Connecting To Tag) if tags.count > 1 { session.alertMessage = More Than One Tag Detected, Please try again session.invalidate() return } let tag = tags.first! session.connect(to: tag) { error in if let error = error { session.invalidate(errorMessage: Connection Failed: (error.localizedDescription)) return } if case let .iso15693(sTag) = tag {
Search results for
nfc
1,175 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Can I use my iPhone to emulate an NFC Tag to transfer data to another iPhone or Android device? No.
Topic:
App & System Services
SubTopic:
General
Tags:
I am trying to transfer data from one device to another using NFC. I'm trying to figure out if this is possible, I downloaded apple's sample project about CoreNFC, I was able to read NFC Tags (it wasn't a real NFC Tag, rather it was an NFC Tag emulated with an android device). Can I use my iPhone to emulate an NFC Tag to transfer data to another iPhone or Android device?
I bought RFID card: NFC 13.56MHz ISO14443A but Iphone can`t read it. What types of RFID card Iphone can read. Is there any specifictaion what cards Iphone can read?
Hi, I was using NFCNDEFReaderSessionDelegate at first to read and write the cards, but didDetect tags method did not detect any tag because my nfc tag is not pre-formatted, it was calling other delegate methods so I have my NFCNDEFReaderSessionDelegate setup correctly. Hence, I used NFCTagReaderSessionDelegate, didDetect tags method of NFCTagReaderSessionDelegate detected tag and the tag was not pre-formatted. The issue I have been facing is I am not able to write for the first time and getting an error Error Domain=NFCError Code=102 Tag Not NDEF formatted UserInfo={NSLocalizedDescription=Tag Not NDEF formatted}. When I used another app from apple store to write data on the same tag which is not pre-formatted. Using that app, I am able to write the data on that tag. That app was using CoreNFC framework I believe, as it has NFC session alert which seems it was from apple library CoreNFC, so I assume that there must be a way to write the data on unformatted nfc tags. Do I have to use
Provisioning profile doesn't include the com.apple.developer.proximity-reader.payment.acceptance entitlement, I did confirm that bundleID capabilities of NFC added and also update the profile on developer console. I cannot use that specific key in entitlement. which steps or missing in this Tap and Pay capabilities I cannot identify.
It appears there might be some confusion or potential issues related to App Clip size and support for digital invocations. To address these issues and ensure your App Clip meets Apple's requirements, consider the following steps: Check Deployment Target Settings: Ensure that the App Clip target has the correct deployment target set to iOS 16.4 or later. Make sure your App Clip target doesn't have any dependencies or frameworks that have a minimum deployment target below iOS 16.4. Reduce App Clip Size: Examine the contents of your App Clip and try to reduce its size by removing any unnecessary resources, assets, or code. Review asset compression settings for images and media to minimize their size. Use asset catalogs to manage and optimize your image assets. If your App Clip contains third-party libraries or frameworks, ensure that they are stripped of unnecessary architectures and resources. Verify Asset Slicing: Confirm that asset slicing is enabled for your App Clip target. Asset slicing is a part of app th
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
We're trying to submit an App Clip with around 17mb, aiming to fit in the new size limit for digital invocations. The mention for the rules can be found in this article.. The relevant part is: If you make your App Clip available on devices running iOS 16.4 and later, your App Clip can be up to 50 MB in size if it meets the following conditions: The App Clip only supports digital invocations — for example, from your website or Spotlight search — and not from physical invocations but like App Clip Codes, QR codes, or NFC tags People use your App Clip in situations where a reliable internet connection is likely, for example, at home Your App Clip doesn’t support iOS versions prior to iOS 16.4 We have updated our App Clip target to have a minimum supported version to iOS 16.4 but when we push it to TestFlight we get an error like below: We identified one or more issues with a recent delivery for your app, (...) Please correct the following issues, then upload again. ITMS-90865: Thinned app clip size is t
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
App Clips
anyway for simple data transfer iphone to iphone via NFC
Topic:
App & System Services
SubTopic:
General
Tags:
Automatically presenting PassKit when approaching an NFC reader has been around for a while on iOS. Apple is already providing support to inhibit this behavior when using an app that has an approval-gated capability with the identifier com.apple.developer.passkit.pass-presentation-suppression. The automatic presentation feature has been added in watchOS 10 without the offering of a similar inhibiting method. This is degrading the experience for watchOS 10 users in use cases where the Apple Watch is expected to be close to an NFC-enabled device. I've noticed that the API is present in watchOS as well, although it's marked as unavailable. Calling requestAutomaticPassPresentationSuppressionWithResponseHandler: is always returning 0 (notSupported), and that might be due to the fact that including the capability breaks code signing. I've opened a FB, was wondering what is the best way to better communicate this need to Apple engineering and product teams. (FB13234179)
I am aware of NFC and UWB api which I have already gone through the official document page. We have to create CCC based digital keys so we are going to use UWB, NFC technologies. So Is there any CCC based UWB,NFC api available for development? We are members of the CCC organization. Could you please support us for this.
We have to create CCC based digital keys so we are going to use UWB, NFC technologies. So Is there any CCC based UWB,NFC api available for development? We are members of the CCC organization. Could you please support us for this I have gone through UWB NFC document from official apple website.But I want to get idea on CCC based NFC and UWBs.
Any news on this? Has anybody successfully taken a travel card and made it work with a static nfc code?
Topic:
App & System Services
SubTopic:
Hardware
Tags:
Greetings, Question 1: I'm currently working on implementing a feature that involves tracking NFC tag reading events. Specifically, I aim to monitor these events for passes that have been added to the wallet using my application. This way, I can gain insights into the interactions users have with these passes and provide enhanced functionality based on their usage patterns. Question 2: Is there a way to implement a restriction on NFC-based passes, allowing them to be used only once for a specific action or purpose? I'm looking to ensure that once a user utilizes the NFC feature associated with a pass, the pass becomes inactive for any future interactions, thereby enforcing a one-time use scenario.
I want to read EMV protocol its possible today with IOS 16 ? its possible to use SELECT or others commands in APDU CoreNFC ? Its possible to interact with 2PAY.SYS.DDF01 ?