@anthroDevChris Based on your post we created a new Settings.bundle and as you said, out of the box it worked! We started to add a couple of items from the original bundle and they worked as well. We tried to copy items from the original and paste them in the new instead of recreating the entire bundle but that didn't work. As soon as we pasted in the old, the entire bundle disappeared in the app settings. We deleted all of the pasted items and it started working again. We ended up recreating all of the previous iitems manually and when we finished, it wasn't showing up again. We deleted one item at a time and found out that the Title type was also causing the issue. We changed all of the Title type entries to Text Field and it resolved the issue. Certainly not ideal. Based on this finding, we tried to go back into the original bundle and change all of the Titles to Text Field but that didn't work either. Seems like there might be some format change with the new bundle file.

We are seeing the same issue. This had been working since 2019 and is critical to the working of our product offering. We don't have any multi-value options in our plist. Installing our app on a device running iOS17 works as expected with the bundle being displayed correctly.

Sorry for the confusion. When I said profile, I meant an actual configuration profile that we're installing on device to limit the networks the iPad/iPhone can connect to. We are trying to use NEHotspotConfiguration to manage the network ("controller") that the device is connecting to out of the list of possible networks ("controllers") established in the configuration profile. Example: The iPad should be able to connect to any of the three Controllers via NEHotspotConfiguration: iPad/iPhone Configuration Profile Controller1 (SSID, password) NEHotspotConfiguration => Controller2 (SSID, password) Controller3 (SSID, password) I hope this makes sense. Please let me know. Thank you.