iOS 9.3.2 does not solve problems with sudden restarts and closing applications

iOS 9.3.2 does not solve the iPad Pro problem with sudden closing of applications or unexpected restarts.

Yesterday I told you that some tablets iPad Pro stuck with error 56 after the installation of the new version of the operating system, users were also unable to use their products because a method to reinstall the operating system does not exist for now.

Apart from this problem, it seems that the same iPad Pro tablets have had problems with sudden closings of applications and unexpected restarts ever since their release during use, some accusing the Safari browser of their appearance, but everything is just a guess.

Although the Apple company has known about the existence of these problems since the beginning of April, in iOS 9.3.2 it did not solve them together with the rest of the bugs solved for users, so people continue to complain on various forums and social networks.

If a user is lucky enough not to get their iPad Pro tablet blocked during installation iOS 9.3.2, he will continue to face sudden closings of applications and instant restarts of tablets, something that no one expects from such an expensive product.

I have started getting random reboots. Today for the first time my 9.7-inch iPad Pro froze on the Apple screen during reboot. It seems to happen most when switching between Mail and Safari. I had to hold the on/off button to get it unstuck. My 9.7-inch iPad Pro (32GB) is less than 15 days old and has exhibited this behavior at least twice now. I'm up to date on iOS. […] Last time [it crashed] I was looking at […] images on Safari. I also had 5-6 apps running in the background.

Of course, Apple has not confirmed the problem in any way and without a confirmation there is no information that would indicate that it will be resolved in the immediate future, but this was to be expected from the American company at the moment.

Unfortunately, Apple has become accustomed to releasing updates for iOS 9 that embarrass it because of the problems it generates for users, and this situation dates back 1 year and does not seem to change soon.