Contents Won't Display

I'm having trouble with the contents tab. When I try to access the contents page of any resource I get a "Sorry" message that tells me:

The application Logos (processcom.logos.androidlogos has stopped unexpectedly. Please try again.

The pop-up screen carrying the message also has a button to force close.

I've tried again repeatedly over several days but the same problem persists. Has anyone else experienced this and is there a "cure?"

Find more posts tagged with

Mobile App

Comments

Dave Hooton

Please clarify what you mean by "Contents tab". How/where did you load the logos application? What version (Settings > Application > Manage Applications & click on Logos)?

ManilaDave

https://community.logos.com/discussion/comment/299405#Comment_299405

The tab is on the top right corner of the screen under the information button. It doesn't matter if it's Logos or Vyrso I get the same sorry message. I've uninstalled and reinstalled both apps 3 times but the problem persists. It's Logos version 21 downloaded from Android Market. Vyrso is version 10 from the same source

Dave Hooton

https://community.logos.com/discussion/comment/311707#Comment_311707

It's Logos version 21 downloaded from Android Market. Vyrso is version 10 from the same source

Android Market should give you the latest Version 0.9.3 - not sure where you got 21 from?

What is your device and version of Android (Settings > About phone > firmware version) e.g. 2.3.3

Hunter Clagett

https://community.logos.com/discussion/comment/311782#Comment_311782

I addition to the above information, it would be great if you could navigate to the Android Market and download an app (it's free!) called CatLog. This allows us to pull some log files from the device.

Once CatLog is installed, try to reproduce the failing links. Once that fails, open CatLog, press the Menu button on your device and then select Send. Email that log as an attachment to yourself.

Please then attach that file to this thread.

Thanks,

ManilaDave

https://community.logos.com/discussion/comment/314600#Comment_314600

Hi Hunter! Thanks, but problem is resolved. downloading the last update fixed the issue.