The Church of Jesus Christ of Latter-day Saints

Printing in the Windows 10 application, while supported, is limited due to shortcomings of Microsoft's WebView control in UWP. WebView2 is being worked on and we hope to integrate it in the future. Once Microsoft releases WebView2 and we are able to incorporate it, we should have much richer support...

This was a bug that was fixed a while back. If you are still seeing this issue, make sure you update to the latest version of Gospel Library. If the issue persists, please send an email to GospelLibrary-Win@churchofjesuschrist.org to report the issue.

There have been issues with the Gospel Library Annotation service and stability. If your annotations seemed to have disappeared, try logging out and back in again at a later time when the service has been restored and you should see them all return.

There was a change made to the Church's authentication system in late October which invalidates all the tokens for the app. You will need to sign-out and back in again for new tokens to be issued and for syncing to resume. It may warn that unsynced annotations could be lost if you sign-out, but in t...

We plan to incorporate study plans into a future version of the Windows 10 app, probably after the sync issues are fixed or implemented on the other platforms first.

Have you tried logging out and back in again?

Well, no is pretty definitive...seems like there may be a way to do it. Here is how I use Gospel Library for Windows on my Mac and on my iPad. I have it installed on a Windows Desktop machine at my home and then I remote desktop into it. Seems to work pretty well for my needs. If you want to try a s...

I'm not sure if there is something specifically missing from the Windows 10 Home N version that would cause an issue, but I suspect it should work fine. There is a new update shipping (v5.0.8) of Gospel Library. See if that version works better for you. If you are still having issues, send an email ...

The beta version 5.0.7 was using a new target that caused issues with individuals running an older version of Windows 10 (1803). It is a strange Windows bug, however, we have figured out a work around and shipped an update in 5.0.8 which allows it to run on Windows 10 (1803) devices.

There is an updated version just releasing now (v5.0.8). I have been testing this on pre-release versions of windows (1903), older versions (1803) and on the current version (1809) all successfully. I have created a Hyper-V instance of Windows 10 1803 VM and tested on that instance and it works ther...