Finally, I've re-installed from scratch. The device was very slow to connect to the wifi's but after an upgrade to the latest version beta, all came back to normal. So I do not know what really happened, except that it is configuration related, which has an influence on the behaviour of the os.

Update to version 17.3 beta2 (I know, I was before they retired it). But the issue remains, and after playing a lot, I was able to remove the device stolen option. I removed all my local networks, but no luck. As the device doesn't connect to any network, and the active wifi is enable when you have luck. You can't edit the settings of a wifi connection. The only action that I am allowed to do was remove the wifi networks. Once I have the luck that I can activate wifi (toggle button is enabled), the device doesn't detect any network around me except the personal hotspot of the iPad or other iPhone devices. But there is no way that the device connects to it. The apple watch added a network, once I updated that device via wifi. But the iPhone still doesn't connect to it. I got the same issue in august this year with an early version of iOS 17. The problem is that the device is well charged and via 4G/5G it takes 32 minutes to do an iCloud backup. Via the lightnin cable it only goes to 5% of the full backup. And it reboots, reconnects to the mobile provider (4G/5G), and after 1/2h we are back to the automatic reboot. Every day the device is posting a crash dump in the feedback portal, but no activity at Apple side.

It seems to be related to the stolen device option. As it doesn't find one of my networks, it assume that the device is not in a known location and it protects himself. Can't reset it, cause there is a delay of 1h, but within that time the device reboots and we are back to the beginning.

Updated to iOS 17.3 (21D5026f), before the season holidays, still worked one week before I took off. I come back to the office and the problem starts again. Problem is that I can't access the screen to disable Private Wifi-Address. But I am convinced that it is related to the iCould config. Cause during the holidays, I needed to confirm my iCould account again on my macOS,and I assume that there the hack is coming into the game. I further investigate via the console to see where the problem is really occurring.

Upgraded to iOS17 - Beta 7, executed the procedure to solve the iCloud backup, but still an issue (described in the release notes). No backup within the reboot period of about 1/2 hour. Device is a 256GB, with about 160GB of apps/data on it. It is also hard to install the developer tools in it via Xcode. For some reason, the device connects/disconnect and so on from the macOS.

Upgrade to iOS 17 - beta 6, same issue. At the beginning, I could select one of my wifi networks, but the connection didn't do it. While I am sure that the passwords were correct. WPA2 and WPA2/Enterprise are currently the security selections I have. The device reboots frequently, taking a backup doesn't succeed in time. (between 2 reboots)

Did a full reset all the data on the device, but no solution yet.

End of the story, I rebooted multiple times my iPhone on Sundays after that he went in his reboot mode. Quite difficult, cause you have to be fast to start the forced reboot before the crash reboot happens. But since the whole bunch of reboots, even in diagnostic boot, but I didn't got a Mac to link the device on. Once the device came back into the normal mode, the automatic crashboots stopped showing themselves up.

Wrong conclusion, cause I de-activated them all, and the problem comes back. It was just a coincident that the reset happend at the moment that the automatic recycle/restart of whatever application happens

Updated to Beta 2 and the issue is still present. Every day, and now I am sure at 8 o'clock it starts. I will try on Monday to connect the console before 8 o'clock, to see what is triggering this. It's very annoying, cause when you debug an application, you need to wait until this cycle, which is something for about 2 hours, last.

Finally, It has nothing to do with what I am looking for, because around 8 am it's start and the problems solves him selves around noon. This has become a daily habit. I don't really see what is going on.

Issue came back this morning, without any action on the device. And its reboots faster than before. As long as you don't identify yourself after the first reboot, it remains in his normal working state. As from the moment you introduce your pincode, the device starts rebooting once the notifications are loading/loaded. Same as yesterday, I don't have a lot of info in the console that helps me finding out what is happening.

Finally, it seems to be related to the accessibility functionalities. Cause when voice over is activated on the watch or on the device you have this issue.

You will see that option after the update