New Version(s) of iOS Apps Not Recommended.

Please keep in mind, I use bunches of apps (art, reading, music, mapping, geology, etc). I don't have any need to leave them in memory and only the Logos apps (as usual) mis-behave.

It didn't misbehave by just being in memory, rather it only had problems if you tried to use it while the servers were down.

Again I pose the question, why is returning a reader to a read page so hard for Logos coders?

Again I say, leave it running if you want to return to the same spot immediately. 

I like that it resets itself when I kill it---usually when I have to do that it's because I have a misbehaving resource (or whatever), and I don't want it to go back to where it was. Besides, many other iOS apps do work this way (clearly the Kindle app isn't one of them).  Maybe it's because I use buggy apps that need this ability to be easily reset.

(Needing to reset the app is another story altogether.  Maybe if I didn't have problems regularly, then I would be more apt to agree with you on this point.  But I'm a beta-tester....)

Todd ... I get the feeling you don't stress your iPad too much.  Some of my apps put 6-8g out, forcing everyone out.  They way they do that is to open multiple versions (e.g. organs).

You'd be wrong.  I have dozens of large apps.  Full catalog astronomy apps, Logos, Kindle, photo editors, Google Earth, games like Minecraft that can eat up tons of memory.  However, it's not hard to stress an iPad: Safari is the worst offender---it's easy for a large web page to use up all RAM in the iPad.  Google Earth crashes regularly from lack of memory if you view it at the wrong angle.

Some of my apps put 6-8g out, forcing everyone out.  They way they do that is to open multiple versions (e.g. organs).

Not sure what you mean here.  6-8g?  organs? what does that mean?

I honestly have never heard of someone wanting NOT to return to where they were reading.  And maybe my experience with Logos apps has been pretty bug free.

I'm not saying I don't want to return to where I was reading.  I do.  But I leave the app in memory, and it works fine when I return to it.  Last week was a fluke. 

The Logos app is not killed by running other apps.  The state is saved when other apps are running. It may not be in active memory, but it is virtuallized to flash memory when there isn't enough space in RAM.

I think you do have a point.   It would be nice if the app would remember where it was after a restart. There can be other ways to reset it.  However, there is no need to kill the app for safety reasons, and in normal usage (leaving it running in the background), it does return to where you were.

See below....the app does return to where it was after a restart of the app.

I am using 4.4 of the app in Verbum and Bible (Logos) and if I close it with a book, it opens to that book.  If I close on library or home screen that is where it opens.   I am using an IPad Air.  

Well I'll be.  It does.  And so I don't know what we're arguing about.   I just tested it on both my iphone and ipad.  Killed the Logos app, and it returned to where it was in the book I had opened.

I recently reinstalled the Logos app for iPad (the audio Bibles were buggy after the outage) and all my books still open at the last page read (even those I last read before the reinstall).

FWIW I'm using Bible! on the iPad mini, no problems like you describe with v4.3.7.  And I never have.

1.  Do you get the black stripe at the bottom?

2.  Where does it send you?

3. Are you operating without internet?

I'm running Bible! 4.4.0 (RC2) as a beta tester.

I rarely get the black stripe.   Faithlife calls it a "toast" popup with the furthest read info in it..  I believe it only appears if you're opened the app to an earlier location than the furthest read location (which usually means you've opened it on more than one device or computer), but I'm having trouble causing it.  I finally got it (pic below), but I'm not sure how.  Seems buggy.  However I rarely find the need to tap on it, as I am usually where I want to be (it disappears after a few seconds).

So as to where it sends me, I can't answer definitively, but it did not send me to the beginning of the chapter when I tapped on the one above.

(I am running with internet).

Also, based on the release notes (on the App Store), the furthest read "toast display" has been around since at least 4.3.0.

Faithlife should explain the functionality of the Furthest Read "Toast" a bit better, I believe.

But I suspect, given all the defensiveness by beta testers, that I'll need to just plan ahead for the Logos apps not returning me correctly.  Kindle it.

Sorry if it felt defensive, but my beta-tester status had nothing to do with my response other than the fact that I'm alrady running 4.4, and  we do need to be clear as to what is happening and why.  You started off by saying were killing the app all the time because of the problems from last week.  That is a side issue, I suppose, but it seemed to me you were introducing problems into the mix that didn't need to be there.

Also, if you are always offline, then that's an important difference from most users.  Logos has changed the way metadata is downloaded and stored in v4.4, and so if you run offline all the time, you may have not gotten all the metadata updated.

The Logos disaster is indeed germaine. You wanted me to leave the apps in memory.  The minute I accidentally go to them, they touch base with the mother ship.  That's not a workable situation, given Logos' inept management of server architecture (surprising us all).

Denise, are you're saying you actually delete the app completely from the iPad to prevent the app from running?  And then reinstall it again from the App Store when you want to use it? ---Excuse me if I'm misunderstanding, but I can't think of any other way of preventing the app from accidentally starting.  Just killing the process doesn't prevent you from accidentally tapping the icon.  Also, didn't you say you were running offline all the time?  Shouldn't that be good enough prevention of any unwanted server contact?

EDIT:  You updated your comments.

Yes, I'm a re-editor. [8-|]

Double-hitting the control button and then fingering them 'up'  (just to be clear).

Okay, good.   As it has been shown that killing the app doesn't prevent it from returning to the same location (at least for others), I won't press the point.  It seems you are having issues others aren't.

So have you ever started up the app while the iPad was online since you upgraded to 4.4?  If not I might suggest it.  The Bible! beta release notes: indicated: "Internal changes related to how resource metadata is stored. This will eliminate the need to update downloaded resources when only metadata has changed. The first run after updating may take up to 20 seconds per 100 downloaded resources to upgrade."  I assume that's still applicable even though it's not noted in the App Store version history for Vyrso or Noet.

I expect and desire all of my apps to re-open in the same place that I left them UNLESS I close the app by swiping up in the multitask menu. When I do that, I expect that it will re-open in a virgin state—at the home page or whatever is the default. This is normal behavior on iOS.

You may want to give this a read: http://www.speirs.org/blog/2012/1/2/misconceptions-about-ios-multitasking.html