_NSURLErrorNWPathKey=unsatisfied (Denied over Wi-Fi interface), interface: utun6, ipv4, dns, uses wifi, LQM: unknown}

Question

lusialfi OP

Created 2d

Replies 2

Boosts 0

Participants 2

Hi there,

When running the app, I found on my Firebase Crashlytics, sometimes got error like this when using Wi-Fi:

Error Domain=kCFErrorDomainCFNetwork Code=-1009 "(null)" UserInfo={_kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=50, _NSURLErrorNWResolutionReportKey=Resolved 0 endpoints in 1ms using unknown from cache, _NSURLErrorNWPathKey=unsatisfied (Denied over Wi-Fi interface), interface: utun6, ipv4, dns, uses wifi, LQM: unknown}

I've run through the threads, found this link, but I think this issue is different on the interface.

It would be great there is and idea how to troubleshoot this issue. Thank you.

Answered by DTS Engineer in 865919022

Denied over Wi-Fi interface is interesting because, by default, iOS apps are always allowed to access Wi-Fi. However, there are exceptions. The most confusing one is the one discussed in this post.

Are these failures correlated with devices in China?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

23h

Recommended

Denied over Wi-Fi interface is interesting because, by default, iOS apps are always allowed to access Wi-Fi. However, there are exceptions. The most confusing one is the one discussed in this post.

Are these failures correlated with devices in China?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

lusialfi OP

7h

Hi Quinn,

Thank you for your feedback.

I have reviewed your suguested post. Unfortunately in our case, I cannot verify whether these failures were correlated with devices in China or were bought in China. From Firebase Crashlytics I can only confirm that these failures occur during networks call while the device is on Wi-Fi.

Initially I suspected these failures were related to SSL pinning, but after reviewing the Apple's documentation and comparing it with our implementation, it appears to follow the recommended best practices. So at this point I still haven't identified it.

Regards

0