iOS 10 regression: HomeKit gets stuck in state where HMHomeManager returns empty array of homes

Originator:brentt4
Number:rdar://28568875 Date Originated:9/30/2016
Status:Open Resolved:
Product:iOS Product Version:iOS 10.1 [14B55c]
Classification:Serious Reproducible:Always
 
Area:
HomeKit (Home app)

Summary:
In iOS 10, HomeKit can frequently get into a state where HMHomeManager returns an empty array of homes, even when some homes have already been set up.

Steps to Reproduce:
0. iOS 10
1. Have a HMHome set up.
2. Have remote HomeKit access enabled via Apple TV login.
3. Turn off Wifi, open (Apple's) Home App to access home remotely.
4. Wait a few seconds.
5. Turn on Wifi, open (Apple's) Home App to access home locally.

* These repro steps have worked to reproduce the issue consistently for me on my home network with my personal HomeKit setup. A friend has the identical problem with his setup. Otherwise, I'm not sure how transferrable they are.

Expected Results:
HMHomeMangager should return the array of homes it had before remote access was attempted.

Actual Results:
HMHomeManager returns an empty array of homes, even seconds after the HMHomeManger gets initialized and its delegate set. homeManagerDidUpdateHomes: is never called.

Version:
iOS 10.1 [14B55c]

Notes:
This bug is in both the public 10.0.2 [14A456] release, and remains a problem in the beta seed of 10.1

Configuration:
iPhone 6S (64 GB) AT&T, on wifi and cellular

Comments

I have been able to resolve this issue by logging out of iCloud on my 4th generation AppleTV and logging back in (for Remote Access).

By brentt4 at Oct. 3, 2016, 7:10 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!