BUG: Safari Reader no longer works on 1.7.17-3
lonkelle opened this issue · comments
Safari Reader no longer works after the latest SafariPlus update. Safari doesn’t Crash at all but I can’t use Reader anywhere without the screenshot attached error showing up immediately.
- iPhone 12 mini, iOS 14.1, Taurine 1.0.5, SafariPlus 1.7.17-3
I have a hard time believing that Safari Plus causes this issue, can you make sure it does not happen when you have Safari Plus disabled in it's preferences?
@opa334 You were correct. I uninstalled Safari Plus, problem still persists. So I guessed it was some other tweak. I entered safe mode and tried to use Reader. Didn't work. So then I figured it could just be being in JB mode altogether. So I rebooted the phone and went to Safari immediately to use Reader, and all sites display the exact error you see pictured. But Safari Plus just injects into Safari...it doesn't change anything permanent. Maybe it was the Taurine update to 1.0.5 recently that did this since that does change files. 🤔 Any thoughts on your end (since I imagine you're a Safari expert - you immediately knew that wasn't Safari Plus' issue for example)?
In the meantime, I'm gonna try to get ahold of other Taurine users now to see if they're experiencing anything similar to this on iOS 14.1 w/ Taurine.
This error is shown if the WebContent XPC service crashes, the reason I knew Safari Plus wasn't causing this is because while Safari Plus does have a dylib injecting in WebContent, it's only used for getting the active video URL (for video downloading) and it can't really break reader mode. Anyways if it also happens in non jb mode then I presume some corrupted cache is causing this crash. Maybe try the "Clear History and Browsing Data" option in Settings under Safari.
@opa334 Thank you for the lower-level explanation. I tried what you suggested but no dice. Tried a few more things, but this is just gonna be one of those "Restore rootFS" moments and getting your opinion helped me make that decision so I'm v appreciative.
Thanks for your help, opa!
Just wanted to add this to everyone out there. Somehow this was fixed by updating to Taurine 1.0.6 (I updated libhooker at the same time but that's not super relevant because the Safari Reader bug still existed in "jailed" mode).
I wanted to document this and felt this was the best place to do so.
Woo for not having to rootFS!