Good day everyone, We have an app containing App Clip which should appear after scanning an URL from an NFC tag. Now if the tag contains ONLY one NDEF URL Record, the App Clip appears. But if there are more fields (as in our case), while URL record being still the first. App Clip is not started, iOS tries to open URL in safari. Is there might be official statement from Apple on this? Could not find any reference in the docs.

I am trying to configure App Clip Experience URL in App Store Connect and it gives me this error message and does not allow to proceed: This URL is not contained in your app’s associated domains. Update associated domains or use a different URL. I have already investigated different options why it can fail and also validated the file over third-party validators. So this is already checked: AASA file available on my domain Content for app clips and app links is specified (see below) Team ID is correct JSON is properly formatted Content Type JSON is specified AASA file visible over Apple CDN https://app-site-association.cdn-apple.com/a/v1/ I waited enough hours after last change Target domain entered into Associations List in Xcode in both main app and App Clip target App bundle with updated Associations is uploaded to App Store Connect I have created Apple TSI yet got no answer for a week already. Any other ideas what I can check? AASA file content: "applinks":{ "apps":[ ], "details":[ { "appID":"8KDIE88JJ.com.baraboo.app", "paths":[ "NOT /_/*", "/*" ] } ] }, "appclips":{ "apps":[ "8KDIE88JJ.com.baraboo.app.Clip" ] } }

It was announced in CoreNFC Video on WWDC that starting from iOS 14 sendRequestWithFlag() command is available as a "write through" interface to transceive commands directly to a tag. There was previously a method customCommandWithRequestFlag() however this was considered to be not working when Addressed Mode (Flag Byte bit mask 0x20) is used. I must use addressed command according to NXP SLIX2 data sheet to authenticate at the tag. So after customCommand..() was not working for me, I tried sendRequest...() but it is also not working, returning NFCError Code=102 "Stack Error" in the case where I consider to be the proper message. The trick at ISO15693 protocol is that after each custom command there should come a byte equal to manufacturer ID. From my experiments I saw that customCommand..() method seem to add this byte by itself. So with this approach non-addressed commands do work. In addressed mode, the full UID should come additionally after the manufacturer ID byte. It is not clear from description of the sendRequest() method if it will add anything on its own or not. Therefore I do not know which parameter I need to add and I experimented with adding/not adding manufacturer ID and/or UID but it either returns the error above or "transceive failed". Is it possible to make open the behaviour inside the sendRequest()? I have a proof that the command works with this tag because the same request executed on android works immediately.