NFC CPSErrorDomain error 2.

Question

Created Jan ’21

Replies 5

Boosts 0

Views 1.5k

Participants 4

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.

Answered by joker45 in 657362022

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.

Boost

Answer 1

Engineer OP

Apple

Jan ’21

Have you tried specifying the full URL scheme http:// or https:// ?

0

Answer 2

joker45 OP

Jan ’21

Accepted Answer

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.

1

Answer 3

joker45 OP

Jan ’21

The Problem is not solved. I misclick... and not able to undo this??

0

Answer 4

Stef-R OP

Jan ’21

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!

0

Answer 5

mihajlo OP

Feb ’21

any solution for this problem so far?
we've got the same error message and are unable to find the solution for nfc read.

qr scan works though..

0