iPad freezes frequently with Mounce’s Complete Expository Dictionary of Old and New Testament Words

Matt Ediger
Matt Ediger Member Posts: 20 ✭✭
edited November 21 in English Forum

Hello, 

My iPad Pro 12.9” (5th Generation) began having trouble this weekend. I am running iPadOS 17.0.1. I am not sure If I had the issue on 17.0 since they came out so close together.  It seems to only happen when I use Mounce’s dictionary. It happens when I accesses this source from a generated word study. However, this morning it froze when accessing that resource from an exegetical guide.

I have hard restarted the iPad. No change. I deleated and reinstalled the app Sunday and the issue reoccurred. No change.   

I don’t seem to have the same issue on my iPhone which is running iOS 17.0.1 as well. 

I imagine someone may ask me for my logs. If so, could you tell me how to send them.

Thanks for advance for any help. 

Tagged:

Comments

  • Joe McCune (Faithlife)
    Joe McCune (Faithlife) Member, Logos Employee Posts: 1,134

    Hi Matt,

    I am sorry to hear that you are having this problem.

    Please do the following to send us your logs.

    1. Open the app.
    2. Tap the Menu icon (this icon has three horizontal lines).
    3. Tap Help.
    4. Press “Report a Problem”
    5. A pre-addressed email will open with a log file attached automatically. Mark it Attention: Joe.  Press “Send” to send your report.

  • Matt Ediger
    Matt Ediger Member Posts: 20 ✭✭

    Joe,

    Thank you for the help. I will have to delete the app again in order to do this. Every time I open the app it defaults to that resource since that is where it froze. Anyway, if I delete the app will that reset the log?

    Thanks again for your help. 

  • Emory Horvath
    Emory Horvath Member Posts: 39

    This is the exact same bug i have periodically on my Samsung Android tablet.  It happens with certain books, often language-related books but sometimes other books as well.  Just had the bug again today.

    After 45 minutes of constant loads/unloads and random clicking, the app eventually gets to a random state where i can load a previously saved layout and get the app back into a working state again.

    It would be really nice if Logos could track down this crashing bug and fix it.

  • Joe McCune (Faithlife)
    Joe McCune (Faithlife) Member, Logos Employee Posts: 1,134

    This is the exact same bug i have periodically on my Samsung Android tablet.  It happens with certain books, often language-related books but sometimes other books as well.  Just had the bug again today.

    After 45 minutes of constant loads/unloads and random clicking, the app eventually gets to a random state where i can load a previously saved layout and get the app back into a working state again.

    It would be really nice if Logos could track down this crashing bug and fix it.

    I am sorry to hear that you are having this situation, Emory.  I would appreciate it if you could send your logs:

    1. Open the app.
    2. Tap the Menu icon (this icon has three horizontal lines).
    3. Tap Help.
    4. Press “Report a Problem”
    5. A pre-addressed email will open with a log file attached automatically. Mark it Attention: Joe.  It would be great if you could mention the titles of books that have behaved this way.  Press “Send” to send your report.

  • Emory Horvath
    Emory Horvath Member Posts: 39

    How much past history do the logs contain?  Because when the issue happens, Logos is extremely unstable and nearly all functions are broken, thus the SendLog function is likely broken too.  So i probably cannot send a log until after i've eventually re-stabilized the app.  That might be too late.

    I attempted to do the ReportAProblem just now, but i'm not sure any email was actually sent.  I don't do emailing on this tablet, so my email may not be configured correctly.  At any rate, i cc'd myself as well but haven't received anything yet so i suspect nothing was sent.  Bummer.

    (Hmm, just checked and there it sits in the Outbox on the tablet's email and refuses to go anywhere.  I'll have to investigate.)

    (Okay, i looked at the log and it doesn't go back far enough.  Next time this happens, i'll send the log more quickly.)