Host_expiry_settings are deleting iOS devices due to never checking in

[rebeccaui]

Fleet version: 4.62

Web browser and operating system: iOS

---

💥  Actual behavior

Host_expiry_settings have been causing several enrolled iOS devices to be deleted after the host_expiry_window has been reached.

🧑‍💻  Steps to reproduce

1. TODO
2. TODO

🕯️ More info (optional)

N/A

[JoStableford]

Linked to Unthread ticket:

Potential issue with iOS devices and host expiry logic #4131

[rebeccaui]

@lukeheath This seems like a P2 or P1 bug.

[sharon-fdm]

@rebeccaui, after the deletion, if these hosts communicate back, are they being returned?
If so, is that not the expected behaviour?

@lukeheath, if approved P2 (or P1) I'll try to pull it in.
cc @noahtalerman

[ddribeiro]

@sharon-fdm, do iOS devices regularly communicate with the Fleet server? Since there is no fleetd agent for iOS devices, all communication is handled through MDM commands which I think need to be initiated from the Fleet server. I don’t believe the devices would communicate back on their own. And since they’re removed from Fleet, we can’t initiate that communication from the server.

[dantecatalfamo]

@rebeccaui What is the intended purpose of host_expiry_settings ?

[rebeccaui]

@dantecatalfamo The host_expiry_settings section lets you define if and when hosts should be automatically deleted from Fleet if they have not checked in.