PocketBible app unable to run, crashed.

Discussion in 'Jailbreaks and iOS Hacks' started by bistechie, Dec 9, 2015.

  1. bistechie macrumors newbie

    Joined:
    Dec 9, 2015
    #1
    In need of help from you Gurus out there. I am on iphone6plus with a jail broken IOS in 8.1.2, can point me in the right direction of a fix please?

    After my (most probably recent updates in Nov) -
    1) opener
    2) browser changer
    3) cephei
    4) flip switch
    5) Techsupport framework
    6) cydia substrate
    7) libpackageinfo


    My pocket bible, all renditions be it 3.37 or 3.4 R unable to run. It will load, then it exit.

    If I uninstall and reinstall, the app will launch for the first time and I can use it. But once it's closed and reopened, the problem comes back.

    I looked at crash dump and I gave the info to the developers. They responded with the following:

    Here's the top of the stack dump, symbolicated:

    0 libsystem_kernel.dylib 0x0000000197110eb8 semaphore_wait_trap + 8
    1 libdispatch.dylib 0x0000000196ff6a4c _dispatch_semaphore_wait_slow + 252
    2 libAXSpeechManager.dylib 0x00000001959e678c -[AXSpeechManager dispatchSpeechAction:] + 64
    3 AXSpeechImplementation 0x000000018459e2a8 -[AVSpeechSynthesizer(Implementation) init] + 188
    4 PocketBible 0x00000001001efa48 -[SpeechState init] (SpeechState.mm:180)
    5 PocketBible 0x00000001001ef974 +[SpeechState sharedSpeechState] (SpeechState.mm:155)
    6 PocketBible 0x00000001000a4490 -[PocketBibleViewController reinitialize] (PocketBibleViewController.mm:2198)
    7 PocketBible 0x00000001000a41c8 -[PocketBibleViewController init] (PocketBibleViewController.mm:2111)
    8 PocketBible 0x00000001000a4128 +[PocketBibleViewController sharedController] (PocketBibleViewController.mm:2071)
    9 PocketBible 0x00000001001a9a38 -[RotatingContainerView createUI] (RotatingContainerView.mm:828)
    10 PocketBible 0x00000001001a8d58 +[RotatingContainerView factoryWithFrame:] (RotatingContainerView.mm:407)
    11 PocketBible 0x00000001001ac37c -[RotatingContainerViewController loadView] (RotatingContainerViewController.mm:211)
    12 UIKit 0x000000018a9f8840 -[UIViewController loadViewIfRequired] + 84
    13 UIKit 0x000000018a9f87ac - [UIViewController view] + 28
    14 PocketBible 0x00000001000a267c -[PocketBibleAppDelegate launch] (PocketBibleAppDelegate.mm:1710)
    15 PocketBible 0x00000001000a1934 -[PocketBibleAppDelegate application:didFinishLaunchingWithOptions:]

    We start at the bottom with PocketBible's application:didFinishLaunchingWithOptions:. That's the first time we get control from iOS. As you work your way up, we're creating our user interface (RotatingContainerView and PocketBibleViewController). During initialization of PocketBibleViewController, we create an AVSpeechSynthesizer object to manage speech. All we're doing at this point is setting its delegate, but it fails during the creation of the AVSpeechSynthesizer object. It appears iOS is waiting on a semaphore that never gets set, so it times out and you get the "failed to scene-create in time" because the app is taking too long to launch
     
  2. darricksailo macrumors 601

    darricksailo

    Joined:
    Dec 18, 2012
    #2
    Before we rule it out as a tweak related problem, trying booting up the device in cydia substrate disabled mode

    hold the volume up button while booting to enter cydia substrate disabled mode

    check and see if this app still crashes. if it does not, then the best way is to remove your most recently updated tweaks one at a time until you find out which tweak is causing the problem

    if it does, then that means the version of the app you have has a bug or the version of the app has some sort of conflict with the jailbreak. Check and see if there is an update for any bug fixes for that app. Try and find a different version of the app from the web and see if the app still crashes
     
  3. bistechie thread starter macrumors newbie

    Joined:
    Dec 9, 2015
    #3
    You are right.

    I managed to fix it.
    I installed cydia substrate update 6110 and the problem occurred.

    Details of the update:

    0.9.6100 blocks extensions on iOS 9 that are guaranteed to crash some key processes (such as Cydia), will inject into too many processes (due to a mismatched filter), or which will lead to subtle bugs (by invalidating the codesign of the target process). This new version also fixes some issues developers were seeing attempting to hook functions in particularly well-sandboxed processes, and adds support for the latest version of Cycript (which now runs Substrate as an injection vector).

    0.9.6101 fixes an issue where Cycript could not inject into a 32-bit process. (This bug might have affected Substrate in some more general way? I am not yet sure about this.)

    0.9.6110 fixes an issue where extension that are corrupt (often on purpose by the developer for obfuscation purposes :/) cause Substrate's attempt to detect whether the extension will cause the process to crash to actually just cause Substrate to crash :/. (In addition to all of the usual numerous improvements I make every time I cut a new release.)

    After I revert back to 6101, the problem disappeared.

    Just so that anyone who has problem can get help.
     
  4. bistechie thread starter macrumors newbie

    Joined:
    Dec 9, 2015
    #4
    Hi Darrick,
    Thank you! You are right. Cydia Substrate is the culprit.

    I managed to fix it now after following your guidance. But I didn't bother starting in 'safe-mode'. Went ahead with the uninstall and revert to earlier version.


    I installed cydia substrate update 6110 and the problem occurred.

    Details of the update:

    0.9.6100 blocks extensions on iOS 9 that are guaranteed to crash some key processes (such as Cydia), will inject into too many processes (due to a mismatched filter), or which will lead to subtle bugs (by invalidating the codesign of the target process). This new version also fixes some issues developers were seeing attempting to hook functions in particularly well-sandboxed processes, and adds support for the latest version of Cycript (which now runs Substrate as an injection vector).

    0.9.6101 fixes an issue where Cycript could not inject into a 32-bit process. (This bug might have affected Substrate in some more general way? I am not yet sure about this.)

    0.9.6110 fixes an issue where extension that are corrupt (often on purpose by the developer for obfuscation purposes :/) cause Substrate's attempt to detect whether the extension will cause the process to crash to actually just cause Substrate to crash :/. (In addition to all of the usual numerous improvements I make every time I cut a new release.)

    After I revert back to 6101, the problem disappeared.

    Just so that anyone who has problem can get help.
     

Share This Page