Audio Narrator/Text mismatch - BOM

Hi,

Tried to search in the forum if anyone noticed this.

Text: Jacob 2:11 Wherefore, I must tell you the truth according to the plainness of the word of God...
Audio: Wherefore, I must tell you the truth concerning the plainness of the word of God...

rolandmallapre wrote:Text: Jacob 2:11 Wherefore, I must tell you the truth according to the plainness of the word of God...
Audio: Wherefore, I must tell you the truth concerning the plainness of the word of God...

Only the male voice. The female voice gets it right. (No further comment here [smile] ).

I recommend you send feedback through the Gospel Library app. The developers will get it most quickly that way.

Thank you Tried to, but whenever i click the send feedback button, it just opens a blank page (google chrome).
My Gospel Library Version is 4.0.1.0 running on windows 10 desktop.

Not sure this is applicable to the app, but with a plain website a lot of strange problems can be solved by doing two things. In fact, the second has been the most common first response when I have reported a problem with lds.org: 1) Do shift-control-R rather than the simpler control-R to force the page to reload the JS and CSS and not only the HTML; 2) Close the browser, bring up a fresh browser window, delete all cookies, clear the browser cache, close the browser. For good measure, and in case something got left behind, I sometimes will do the second step two or three times.

Okay. Thank you Will try that. And just so you know, when i click the "send feedback" link under the "about" section of the app, it simply opens my browser (google chrome), nothing is on the address bar and it's not showing that it's loading any page. My Gospel Library Version is 4.0.1.0 running on windows 10 desktop.

Text: Jacob 2:11 Wherefore, I must tell you the truth according to the plainness of the word of God...
Audio: Wherefore, I must tell you the truth concerning the plainness of the word of God...

For the record, content issues like these aren't able to be resolved by the developers of the Windows app, as we develop the app and not the content provided in it.

Okay. Thank you Will try that. And just so you know, when i click the "send feedback" link under the "about" section of the app, it simply opens my browser (google chrome), nothing is on the address bar and it's not showing that it's loading any page. My Gospel Library Version is 4.0.1.0 running on windows 10 desktop.

See my response to someone else having the same problem with Chrome here:

http://tech.lds.org/forum/viewtopic.php ... 61#p173261

ToManyLetters wrote:For the record, content issues like these aren't able to be resolved by the developers of the Windows app, as we develop the app and not the content provided in it.

Would it be too rash to assume you have the email for the content people so it can be passed on?

First, I reported the issue last evening to make sure they were aware of the problem. The report has been acknowledged . . .

ToManyLetters wrote:For the record, content issues like these aren't able to be resolved by the developers

. . .and passed on to the content folks as I requested.

rolandmallapre wrote:And just so you know, when i click the "send feedback" link under the "about" section of the app, it simply opens my browser (google chrome), nothing is on the address bar and it's not showing that it's loading any page.

Some versions of the app open the mail client on the device with a preaddressed draft email and troubleshooting files attached.

russellhltn wrote:Would it be too rash to assume you have the email for the content people so it can be passed on?

The developer folks are more than happy to forward content issues to the content folks, and to reply that they have done so. Because I have seen content issues fixed, I am confident that they do forward them on.

Thanks guys I came here because the "send feedback" button didn't work on my computer.

I just read the link ToManyLetters shared, thanks. I think that should resolve the button issue. Will try it later.

And it did work! just tried it. My default app for email was set to google chrome. I changed it to Windows Mail. The "send feedback" button works now. Thanks again!

Some versions of the app open the mail client on the device with a preaddressed draft email and troubleshooting files attached.

Windows included. Chrome is just stupid and hijacks the default email client spot on users' devices. When this happens, Windows doesn't know how to pass the information on... Or more accurately, Chrome isn't an email client and doesn't know what to do with the information that gets passed to it.

The developer folks are more than happy to forward content issues to the content folks, and to reply that they have done so. Because I have seen content issues fixed, I am confident that they do forward them on.

Although true for the iOS and Android platforms, we don't have the same direct line to the content team and are not able to relay this sort of information. We have, in the past, several times learned of major changes to content distribution by our users reporting, in essence, that the content team broke something again.

Would it be too rash to assume you have the email for the content people so it can be passed on?

It'd certainly make my life easier if I did.

And it did work! just tried it. My default app for email was set to google chrome. I changed it to Windows Mail. The "send feedback" button works now. Thanks again!

Glad to hear it's working for you now!

ToManyLetters wrote:Chrome is just stupid and hijacks the default email client spot on users' devices. When this happens, Windows doesn't know how to pass the information on... Or more accurately, Chrome isn't an email client and doesn't know what to do with the information that gets passed to it.

I wonder what would happen if Chrome were signed into a Google account?

ToManyLetters wrote:Although true for the iOS and Android platforms, we don't have the same direct line to the content team and are not able to relay this sort of information. We have, in the past, several times learned of major changes to content distribution by our users reporting, in essence, that the content team broke something again.

Wow. That's sad.

ToManyLetters wrote:Although true for the iOS and Android platforms, we don't have the same direct line to the content team and are not able to relay this sort of information.

I have the email address for the Android developers if you need it. [grin]
Then again, I don't think they get advance notice of problems either. But certainly all of you should be able to pass content problems on to someone, I would think.

Maybe I shouldn't think.

But certainly all of you should be able to pass content problems on to someone, I would think.

For Android and iOS who have paid developers who work at the Church Office Building, sure. For the volunteers who contribute to the Windows platform, no. For all the luck we've had getting a firm line to the content team, we might as well just scream into the void.

ToManyLetters wrote:For all the luck we've had getting a firm line to the content team, we might as well just scream into the void.

I think personally I would start sending notes to the Android or iOS team asking them to forward content information for you. You could alternate. Equal opportunity.

Of course, it would probably be helpful if you knew more about how the content team was preparing content for you to display. I see what you mean when you say that the content team broke something again. They probably will continue to do so. But if you had advanced warning that the break was coming . . . . Sigh. I feel your pain.

please help? I downloaded Gospel Library 2 weeks ago and it worked fine, now the read along feature isnt found/working ( I guess it is called narrator), does anyone know how to get it back?