trevcanhuman

After watching the new Oppenheimer movie, it got me thinking how vast science and technology is. A lot of things can be used for evil. Maybe the question is not about complete regret or not developing the software at all but about changing how it was developed or for who.

Hello, hn. I come here for help and to document a bug, maybe Apple will take notice of this and will do something about it.

The bug is the following: an iPad Pro (iOS version between 14.x.x and 16.x.x) rejects the correct passcode for the device. I am 100% correct that this is the passcode, it has been the same for the device for more than one year. The device keeps locking me out, saying "Incorrect password". I have had to wait over a day to even try.

After almost giving up, I tried updating my iPad Pro to the most recent iPad OS version at the time (16.4.1).

After that, a Data Recovery screen appeared. It asked for the device's passcode. After entering the correct device passcode it asked for confirmation again, I entered it again and it said that it was performing data recovery. I assume that the device confirmed that the passcode was indeed correct because it did not say anything along the lines of 'incorrect passcode'. Now, the next problem is that after the Apple status bar (like in the updates) ends it says 'Data Recovery Failed'. I tried yet again doing the process of attempting data recovery by entering the passcode and confirming it again, yet it showed the same: 'Data Recovery Failed'.

I then tried to restart the device, did successfully and then showed a screen that said: 'Try again in 8 hours', just like the passcode screen that tells you to wait until you can try again.

Any suggestions on trying to debug this ?

Does iOS Safari also crash on your iPhone ?

About a month ago I got this weird crash on Safari on my iPhone 6s. Everything was working fine. I was just searching on duckduckgo and all of a sudden I get this [0], [1]. "A problem repeatedly ocurred on $URL" Now all my safari tabs crashed. I hit refresh, I change the url. I go to any other website and it still shows the error.

Killing the app does not work. Maybe something to do with webkit ? The only thing that worked the first time was installing the latest iOS update (15.6), I had 14.x.something before.

Search engine: duckduckgo

But the problem is that this issue is very weird. Some apple forums said that disabling javascript would restore Safari. It kinda did.

The first time this happened, it did not work and as mentioned before, o ly a full software update worked.

But guess what ? This bug happened to me today. Which means it has nothing to do with the new ios 15 update. This means it is weirdly reproducible. I don't know what I did or how it happened but it happened again. And for some reason, now disabling javascript worked like a charm and them re-enabling it un-killed the bug. Why ? I don't know.

Also, does anyone know about how to go report this bug to Apple ?

Thanks

references

[0] https://files.thetrevor.tech/IMG_0857.PNG

[1] https://files.thetrevor.tech/IMG_0858.PNG

Does iOS Safari also crash on your iPhone ?

About a month ago I got this weird crash on safari. Everything was working fine. I was just searching on duckduckgo and all of a sudden I get this [0], [1]. "A problem repeatedly ocurred on $URL" Now all my safari tabs crashed. I hit refresh, I change the url. I go to any other website and it still shows the error.

Killing the app does not work. Maybe something to do with webkit ? The only thing that worked the first time was installing the latest iOS update (15.6), I had 14.x.something before.

Search engine: duckduckgo

But the problem is that this issue is very weird. Some apple forums said that disabling javascript would restore Safari. It kinda did.

The first time this happened, it did not work and as mentioned before, o ly a full software update worked.

But guess what ? This bug happened to me today. Which means it has nothing to do with the new ios 15 update. This means it is weirdly reproducible. I don't know what I did or how it happened but it happened again. And for some reason, now disabling javascript worked like a charm and them re-enabling it un-killed the bug. Why ? I don't know.

Also, does anyone know about how to go report this bug to Apple ?

Thanks

references

[0] https://files.thetrevor.tech/IMG_0857.PNG

[1] https://files.thetrevor.tech/IMG_0858.PNG