For some time now my module for Robert Reymond's A New Systematic Theology of the Christian Faith has been failing on mobile. No matter where I open it on my iPhone or iPad, it always opens to this screen (see attached). I have tried to remove the downloaded module and re-download it. I have tried to go to the desktop version (which works fine) and go to a different spot so I can go to "Last Read" in mobile. I have tried navigating through the table of contents. It will not leave this screen.
Which specific version of iOS? The app?
Have you tried moving from scrolling view to paged view (or vice verss)?
macOS, iOS & iPadOS | Logs | Install
Very strange - I’ve just tried it and it works correctly for me on iPad. So it doesn’t look like a resource issue.
JT (alabama24): Which specific version of iOS? The app? Have you tried moving from scrolling view to paged view (or vice verss)?
I am using both iOS 13.5 and iPadOS 13.5 On an iPhone 11 and iPad (7th gen.). This is the only resource it is doing this to.
I tried switching to paged view. However, all it did was make it to where no matter how many times I flipped the page, it showed the screen above.
I suppose I could delete the entire app and reinstall it. But I really want to avoid that, since it would require me to download all my resources again.
Hi Cheryl,
I am sorry to hear that you have been having trouble with this.
Please also do the following:
1. Open the app.2. Tap the Menu 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. Press "Send" to send your report.
We will be able to look into this further, once we have your logs.
Update:
I sent an error report. Not sure if it was ever looked into. Regardless, I seemed to have fixed the problem. I went into every layout that contained this resource and removed it, and then saved the layout like that. Next, I went into my library and removed the downloaded resource. Then, I reset all reading progress. Then I downloaded the resource again.
This seemed to fix the problem!