PreferenceOrganizer2
PreferenceOrganizer2 copied to clipboard
System Apps section not working (iOS 10.3.1, g0blin)
The System App section does not work for me on 10.3.1 with g0blin jailbreak. All other sections are sorted, but the System App section is not there and no system apps are sorted anywhere..
Does this still occur on version 4.0.4 (or whatever the latest version is when you read this)?
On Sat, Jul 21, 2018 at 11:12 AM angelXwind [email protected] wrote:
Does this still occur on version 4.0.4 (or whatever the latest version is when you read this)?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/angelXwind/PreferenceOrganizer2/issues/39#issuecomment-406806980, or mute the thread https://github.com/notifications/unsubscribe-auth/AfY4uncG1Mi8ZLBY3fzFnqNP39gRfQnNks5uI1L8gaJpZM4SR0ni .
System apps section still doesn’t show with latest update 4.0.4
Can you enable debug mode and upload the log somewhere…? I am so confused at how this appears to be something that's actually specific to the jailbreak and not iOS…
Sure https://www.dropbox.com/s/3dvqmsgvucp1w0e/net.angelxwind.preferenceorganizer2.zip?dl=0
On Sun, Jul 22, 2018 at 4:05 PM angelXwind [email protected] wrote:
Can you enable debug mode and upload the log somewhere…? I am so confused at how this appears to be something that's actually specific to the jailbreak and not iOS…
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/angelXwind/PreferenceOrganizer2/issues/39#issuecomment-406896675, or mute the thread https://github.com/notifications/unsubscribe-auth/AfY4usPF7NsHicQx9FbtiRwBJSi0oq8oks5uJOkjgaJpZM4SR0ni .
4.0.4和4.0.5版本,"系统设置"不显示,使用4.0.3可以显示,附调试文件https://pan.baidu.com/s/10-gUzVNksgRWe2em5180dg
系统10.3.3,iphone SE,DoubleH3lix越狱工具
This is a literal 3-year-old issue at this point, but I was not able to reproduce this at least on iOS 10.2.1 (which is the only iOS 10 version I have access to).
What's strange to me is that the change that occurred between 4.0.3 and 4.0.4 was in commit e19459891f7e0357fe7e2694b0d78b8c8ad07f4c, and no changes in there should be able to cause something like this…
(Oops, hit the wrong button there.)