iPhone Highlighting Discrepancy

Any idea what is causing that? I'm hoping it can be corrected easily.

I don't remember seeing this before.

Do you know which is "correct"? Looking at the examples you give I would assume that the iPhone highlighting is as you did it and the PC is not matching it.

My guess is that the resources are at a different level.

Can you check support information for the resource on both systems - click/tap on the "i" at the top-right of the resource and scroll down

Please show the information you got in both cases.

Notice the shift in highlighting between the two in the below examples:

In addition to Graham's questions, what version of the app are you running on your iPhone, and is the resource downloaded or not?

If the resource is downloaded, can you provide a screen shot of the resource info? You can then try deleting the resource and redownloading to see if that fixes it.

to see if that fixes it.

As above I'm not sure that the problem is on the iPhone - it looks more like a desktop issue to me.

to see if that fixes it.

As above I'm not sure that the problem is on the iPhone - it looks more like a desktop issue to me.

why? If the resource that isn't up to date on the mobile device, the highlights might be off when they sync to the desktop. 

why? If the resource that isn't up to date on the mobile device, the highlights might be off when they sync to the desktop. 

Good point[:)]

FWIW - This is one of the reasons why I don't recommend users download LARGE portions of their library. 

Hi Graham. The error occurs "both ways" regardless if I highlight in the PC Logos 6 or on the iPhone.

iPhone 6 resource information is:

PC Logos 6 info is:

Hi Kevin. The resource is downloaded. I am running app version 4.4.2 (4.4.22503)

The resource is downloaded.

Try deleting the resource on your mobile device and see if that fixes things. 

This may be a resource issue rather than a software one... See this screen shot:

This may be a resource issue rather than a software one

Or not. I made highlights from both L6 and the Bible! app in both the "downloaded" and "undownloaded" state... it worked just fine. The screen shot above is a bit puzzling.

Deleted and reinstalled the resource on my iPhone. Issue is still there.

Deleted and reinstalled the resource on my iPhone. Issue is still there.

For clarification: I would expect that previous highlights might still be askew. Are new highlights that way?

Also, what specific version of the desktop app are you using? 

I am running desktop version 6.0b SR-2 6.0.2.0075. New highlighting errors are still occurring regardless if highlights are created on my iPhone 6 or on my PC with Logos 6.

sal, are you using the Scrolling View on your iPhone? Whenever I come across wacky highlighting behavior with the Logos app on my iPad (nowadays I get that quite frequently with random resources) I just turn the Scrolling View off and back on, and that fixes the problem. Though your case seems stranger than any of the issues I've encountered, it can't hurt to try the turn off/turn on thing (or even turn on/turn off - it worked for someone here once).

I tried scrolling view on and off and it did not fix the problem.

Is this problem only in this one resource? I am leaning towards saying that you have a corrupt index on your computer... But that is a wild guess   

I am running desktop version 6.0b SR-2 6.0.2.0075. New highlighting errors are still occurring regardless if highlights are created on my iPhone 6 or on my PC with Logos 6.

We've been able to reproduce the issue with this particular resource but are not yet sure of the cause.

Has this been happening with any other resource, or just On Guard?

I have a fix for this internally. It should be shipping in a beta soon.

Is there an explanation for why this bug affected one user and not another (see my screen shot on page 1)? Does it affect more than the one resource?

It can depend on which combinations of versions of the apps (mobile and desktop) you are running. Yes, it affects more than just the one resource.

Perhaps even more importantly, and unfortunately, is that this bug causes the application to wrongly calculate positions within certain sections of text. Meaning, notes taken in affected resources on affected client applications may actually be wrongly positioned. The fix coming out could bring this to light and notes might now "move" as the bad data is correctly reflected in the display.

Given the necessary combination of resource and application to manifest the bug, I'm hopeful that it has not had a widespread impact on user data. But, it is likely to have isolated instances of this (specially the OP and those of you who have tested on these sections of text).

Alan, thank you for the update. Looking forward to the bug fix. [:)]

But, it is likely to have isolated instances of this (specially the OP and those of you who have tested on these sections of text).

I will try to keep those highlights then. They are in a special document for testing. 

The fix coming out could bring this to light and notes might now "move" as the bad data is correctly reflected in the display.

Yep (Screen shot below)

Base on Bradley's post in this thread, should I be worried about rebuilding my entire index? 

There was a bug in 6.0b and 6.1 betas. If you indexed a lot of resources in that time frame, I would advise reindexing. If not, you should be ok.