Error Domain=ASErrorDomain Code=450 "Current device is not Wi-Fi Aware capable."

Question

Created May ’26

Replies 6

Boosts 0

Views 1.1k

Participants 3

We are currently investigating a serious issue related to Wi-Fi Aware and AccessorySetupKit.

We found that some devices which originally supported Wi-Fi Aware may suddenly report that Wi-Fi Aware is not supported. After this happens, calling the following API fails:

ASAccessorySession.showPicker(for:completionHandler:)

API documentation: https://developer.apple.com/documentation/accessorysetupkit/asaccessorysession/showpicker(for:completionhandler:)

The error returned is:

Error Domain=ASErrorDomain Code=450 "Current device is not Wi-Fi Aware capable.”

Related logs:

error: Error Domain=ASErrorDomain Code=450 "Current device is not Wi-Fi Aware capable."

21:27:33.116061+0800 deviceaccessd Activating DASession: CID 0x7FC70001, BundleID xxxx, PID 542, WiFiAwareSupported: no

2026-05-26 21:27:33.118<103>21:27:33.118[E][WiFiAware::WA]@"":[ASK] showPicker callback error: Error Domain=ASErrorDomain Code=450 "Current device is not Wi-Fi Aware capable." UserInfo={

NSDebugDescription=Current device is not Wi-Fi Aware capable.,

cuErrorMsg=Current device is not Wi-Fi Aware capable.,

NSLocalizedFailureReason=Current device is not Wi-Fi Aware capable.

}

Device information:

Device: iPhone 16 Pro

OS Version: 26.5

The device was previously able to use Wi-Fi Aware successfully. However, after the issue occurs, the system reports:

WiFiAwareSupported: no

The only known way to recover so far is to erase all content and settings / factory reset the device. This is not an acceptable workaround for end users and may cause a severe user experience issue.

We would like to ask for your help with the following questions:

Under what conditions would an iPhone that supports Wi-Fi Aware suddenly be reported as not Wi-Fi Aware capable? Is WiFiAwareSupported: no determined by hardware capability, system configuration, region setting, privacy/security policy, entitlement state, or some cached system state? Is there any known issue in AccessorySetupKit or Wi-Fi Aware on iOS 26.5 that could cause this behavior? Is there a way to recover the Wi-Fi Aware capability without requiring a factory reset? Are there any additional logs, sysdiagnose profiles, or diagnostic commands you recommend us to collect when this issue occurs? This issue is critical for us because users who encounter it will no longer be able to proceed with accessory setup, even though their device should support Wi-Fi Aware.

Please let us know if you need a sysdiagnose, sample project, full device logs, or additional reproduction information. We would appreciate any guidance on the root cause and possible workaround.

Answered by DTS Engineer in 896783022

I’m unlikely to spontaneously update this thread if and when we start seeding a fix.

Hey hey, I lied (-:

This came up in another thread so I took a look at the bug (r. 175178722) and it seems that the fix caught the iOS 26.6 beta 4 (23G5057c) train [1]. So, please make sure to retest on that release.

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

[1] It might’ve been included in previous beta seeds; I don’t have time to check that right now.

Answer 1

DTS Engineer OP

Apple

May ’26

Accepted Answer

We found that some devices which originally supported Wi-Fi Aware may suddenly report that Wi-Fi Aware is not supported.

I can’t imagine that being anything other than a bug.

The only known way to recover so far is to erase all content and settings / factory reset the device.

Yikes!

I believe you’ve filed a bug report about this already (FB22866996), so thanks for that. I had a look at your bug and it’s definitely with the right folks.

Based on the diagnostics you posted here, it sounds like you have access to an affected device. If so, have a read of Filing a Wi-Fi Bug Report to see if there’s anything you can do to improve your bug report.

Also, it wasn’t clear whether you’ve tried to reset the device’s network settings (Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings). If not, you could try that. But:

If you only have one device that exhibits the problem, it’d be better to keep that in the broken state and instead have one of your users try this mitigation.
If you do decide to try this on your one affected device, make sure you grab the above-mentioned diagnostics beforehand.

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

Answer 2

vince-zheng OP

May ’26

Hi ,

Thanks for your response.

Regarding FB22866996, I have already uploaded the report through Apple Feedback Assistant, and a corresponding sysdiagnose log has also been attached. Please feel free to check that feedback ticket for the detailed diagnostics.

I have also performed several recovery attempts on the affected device.

Yesterday, the device appeared to recover temporarily, but the same issue occurred again afterwards. Today, I tried the following actions, but none of them were able to restore Wi‑Fi Aware support:

Reset Network Settings
Reset All Settings
Restarted the device
Tried using AirDrop transfer

At the moment, the device still reports that Wi‑Fi Aware is not supported.

I also tested different pairing scenarios. Based on my current testing:

Wi‑Fi Aware pairing in accessory mode fails. The accessory keeps showing a “Not Supported” message.
However, pairing between mobile phones using Apple’s DevicePicker API works successfully:
https://developer.apple.com/documentation/DeviceDiscoveryUI/DevicePicker

So the issue seems to be specific to the accessory-mode Wi‑Fi Aware pairing flow, while the phone-to-phone DevicePicker flow can still work.

The affected device is still in the problematic state. Please let me know if there are any additional diagnostics or logs I should collect while the issue is still reproducible. I’m happy to provide more information or run any additional tests if needed.

Thanks.

Answer 3

DTS Engineer OP

Apple

May ’26

Thanks for the update.

I’ve been chatting with various engineering teams about your issue. They believe that you’re hitting a known bug. Originally I was skeptical of that conclusion because you wrote:

The only known way to recover so far is to erase all content and settings

which isn’t a good match for the bug they’re talking about. However, in your latest message you wrote:

Yesterday, the device appeared to recover temporarily, but the same issue occurred again afterwards.

which is much like what we’d expect.

Anyway, your bug is now marked as a duplicate of an internal bug tracking this problem. The fix for this is not in any shipping or seeded releases of iOS. If and when that changes, our bugs folks should notify you via your bug.

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

Answer 4

jul19n OP

Jun ’26

I am facing this issue myself. If this thread can also be resolved when there is a seeded release with a fix, that would be appreciated.

Answer 5

DTS Engineer OP

Apple

Jun ’26

Just to set expectations, I’m unlikely to spontaneously update this thread if and when we start seeding a fix. vince-zheng should be notified if and when that happens, and it’d be nice if they posted an update here.

But if you don’t want to rely on them, you can file your own bug about this, asking that it be marked as a duplicate of of our internal bug (r. 175178722). That way our bugs system will notify you if and when there’s a fix.

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

Answer 6

DTS Engineer OP

Apple

2w

Recommended

I’m unlikely to spontaneously update this thread if and when we start seeding a fix.

Hey hey, I lied (-:

This came up in another thread so I took a look at the bug (r. 175178722) and it seems that the fix caught the iOS 26.6 beta 4 (23G5057c) train [1]. So, please make sure to retest on that release.

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

[1] It might’ve been included in previous beta seeds; I don’t have time to check that right now.