Jump to content


Photo

iOS 2.0 Bug: Additional Pane Module Selector Causes Crash

bug crashes module selector crash 2.0 ios 2.0

  • Please log in to reply
5 replies to this topic

#1 Mac72583

Mac72583

    Member

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Accordance Version:10.x

Posted Yesterday, 04:01 PM

Hi, I wonder if anybody else is having this same issue since updating to iOS 2.0. When I try to select a different text to read in the parallel text pane, the app immediately crashes. For example, while reading in BHS-T, the default parallel text is also BHS-T. However, if I try to switch to the NRSV or the LXX by tapping the module selector, the app crashes immediately.



#2 Michael J. Bolesta

Michael J. Bolesta

    Platinum

  • Active Members
  • PipPipPipPipPip
  • 731 posts
  • Gender:Male
  • Location:Addison TX
  • Interests:scripture study, preaching, teaching
  • Accordance Version:11.x
  • Platforms:Mac OS X, iOS

Posted Yesterday, 09:42 PM

I have had this crash too. It is fairly frequent. Restarting the app and trying again usually does not crash the app.


Michael
Accordance on Macintosh, iPhone, and iPad

#3 Helen Brown

Helen Brown

    Mithril

  • Admin
  • 8,744 posts
  • Twitter:accordancebible
  • Gender:Female
  • Location:heart in Israel
  • Accordance Version:11.x
  • Platforms:Mac OS X, Windows, iOS

Posted Today, 08:00 AM

This is happening only to certain users (not to me, for example), and is therefore hard to track down. Please send the crash log reports to our support department.

 

You can access the crash report on your iOS settings. Settings/Privacy/Diagnostics & Usage/Diagnostic & Usage Data/

Find the crash log using the date and time stamps and open it. Long tap the screen and select copy. Stretch the handles to cover the entire report and then copy it and email it to us in support and we will forward it to the iOS programmers to analyze and debug.
 


Helen Brown
OakTree Software

#4 G Springer

G Springer

    Bronze

  • Active Members
  • PipPip
  • 72 posts
  • Gender:Male
  • Location:DuPont, WA
  • Interests:Administrator, Student Services, and Instructor at TorahResource Institute
    OS--Yosemite and Windows (XP, 7, 8.1)
  • Accordance Version:10.x

Posted Today, 12:39 PM

I have had the same experience and have not reported it before now - basically because I've not been able to duplicate the problem "on demand."

I did my rigorous testing this morning and it did crash my iPad app. I went to the crash log area and didn't find a crash log to send.

This crash has happened related to selecting a second pane text about 5 times to me. Every time I've not been able to reproduce it after the app resets.

A difficult bug to catch...I'm thinking it is about like trying to catch a fly with chopsticks...



#5 Mac72583

Mac72583

    Member

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Accordance Version:10.x

Posted Today, 02:10 PM

Hi Helen. Could you tell me what the beginning of the log entry should look like? There are two dozen or so different entries or so that might match up with a crash (there have been many). Thank you in advance.

#6 Mike Garrity

Mike Garrity

    Gold

  • Accordance
  • 384 posts
  • Gender:Male
  • Location:Florida
  • Accordance Version:10.x

Posted Today, 07:08 PM

Hi Mac72583,

 

Accordance Mobile crash logs typically begin with "iAccord_{date}_{device name}...".

 

Mike







Also tagged with one or more of these keywords: bug, crashes, module selector, crash, 2.0, ios 2.0

1 user(s) are reading this topic

1 members, 0 guests, 0 anonymous users


    Mac72583