Gospel Library for Windows 10 Version 4.0.0.0

Discussions around the Gospel Library application for Windows for Desktop and Mobile

Moderator: BowmanDH

21bmedic
New Member
Posts: 3
Joined: Thu Oct 12, 2017 3:29 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#31

Post by 21bmedic »

I just noticed a grammatical error in a note I had taken, so I opened to edit and change, but now it was updated to show the date of the edit, not the day that I originally made the note. Is there a way to find any version history to tell when I originally made the note?
User avatar
sbradshaw
Community Moderators
Posts: 6245
Joined: Mon Sep 26, 2011 9:42 pm
Location: Utah
Contact:

Re: Gospel Library for Windows 10 Version 4.0.0.0

#32

Post by sbradshaw »

21bmedic wrote:I just noticed a grammatical error in a note I had taken, so I opened to edit and change, but now it was updated to show the date of the edit, not the day that I originally made the note. Is there a way to find any version history to tell when I originally made the note?
The date created is stored with each Gospel Library annotation, but isn't currently visible to the user. So, even though it's not displayed, it's still there, and could be made visible in a future app update if it becomes a priority (if it's any consolation).
Samuel Bradshaw • If you desire to serve God, you are called to the work.
zORg_alex
New Member
Posts: 2
Joined: Sat Sep 02, 2017 11:24 am

Re: Gospel Library for Windows 10 Version 4.0.0.0

#33

Post by zORg_alex »

Throws error on loading. And this time it does not give option to send a report, but just to copy this:

The link is broken or the content may be unavailable.
at GospelLibrary.UI!<BaseAddress>+0xf79e1c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at GospelLibrary.UI!<BaseAddress>+0xf8f669
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at GospelLibrary.UI!<BaseAddress>+0xfc1bb5
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at GospelLibrary.UI!<BaseAddress>+0xfc14be
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at GospelLibrary.UI!<BaseAddress>+0xfbc210
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at GospelLibrary.UI!<BaseAddress>+0x140828c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x4d5ce0
at SharedLibrary!<BaseAddress>+0x4d5c68
at SharedLibrary!<BaseAddress>+0x4d5c27
at SharedLibrary!<BaseAddress>+0x54529b
at GospelLibrary.UI!<BaseAddress>+0x140f876
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SharedLibrary!<BaseAddress>+0x65496e
at SharedLibrary!<BaseAddress>+0x4f5158
at SharedLibrary!<BaseAddress>+0x4f54bc
at SharedLibrary!<BaseAddress>+0x4a0ad0
at GospelLibrary.UI!<BaseAddress>+0xf2fb48
at GospelLibrary.UI!<BaseAddress>+0xf2fa84
at Microsoft.HockeyApp.Extensibility.Windows.UnhandledExceptionTelemetryModule.CoreApplication_UnhandledErrorDetected(Object sender, ApplicationModel.Core.UnhandledErrorDetectedEventArgs e)
at System.EventHandler<System.Threading.Tasks.UnobservedTaskExceptionEventArgs>.Invoke(Object sender, Threading.Tasks.UnobservedTaskExceptionEventArgs e)
at GospelLibrary.UI!<BaseAddress>+0x102b566
at GospelLibrary.UI!<BaseAddress>+0x102bd1f

I don't remember what I had opened before that could cause this on loading. I first thought it's because I had no internet connection.
shawnsalisbury
New Member
Posts: 4
Joined: Tue Feb 21, 2012 7:49 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#34

Post by shawnsalisbury »

App has worked fine for quite some time, then last week I cannot open it. I have unistalled repeatedly, done reset, tried this on normal and beta. I cannot open it, it crashes a few seconds after trying to sign in. I'm on Windows 10.0.14393 Build 14393.
Pringles1
New Member
Posts: 13
Joined: Thu Apr 27, 2017 10:24 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#35

Post by Pringles1 »

@shawnsalisbury please check out beta 4.2.3 or prod 4.2.4 and let us know if you still have the issue.
shawnsalisbury
New Member
Posts: 4
Joined: Tue Feb 21, 2012 7:49 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#36

Post by shawnsalisbury »

4.2.4 fixed it, great thanks!!
DokoMadeMo
New Member
Posts: 1
Joined: Thu Sep 20, 2018 11:26 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#37

Post by DokoMadeMo »

Hi! So I just recently installed this app on my Windows 10 PC and it was working just fine for a while but then suddenly out of nowhere it doesn't open the app; specifically it stays stuck on the load screen and it usually finishes loading everything (the green checkmarks are in place) but it doesn't go beyond that. I have tried both resetting and uninstalling/reinstalling the app several times, which works on the first startup, but then the next time I launch the app, it doesn't open completely and gets stuck on the loading screen. Is there any way to fix this so I don't have to keep resetting it? This issue first started happening when upon launching it said there was a catalog update, yet after saying it had successfully loaded the catalog update, it stayed stuck on that screen and it's been having problems ever since. Thanks so much!
smallen5
New Member
Posts: 1
Joined: Thu Jan 17, 2019 10:15 am

Re: Gospel Library for Windows 10 Version 4.0.0.0

#38

Post by smallen5 »

So I had a problem this morning trying to book mark a lesson I wanted to book mark Aaronic Priesthood/priesthood and priesthood keys/what does it mean to sustain church leaders? and instead it book marks "why do we have adversity? I reset the application and it didn't correct the problem. What do I do?
Pringles1
New Member
Posts: 13
Joined: Thu Apr 27, 2017 10:24 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

#39

Post by Pringles1 »

@ smallen5 I just tried to bookmark the content you wanted however for me it worked just fine.

I am on the latest version of the app. Have you tried deleting the bookmark and trying again? What device were you using and what app version?
are you able to reproduce the issue again?
Thanks!
lcheesman
New Member
Posts: 2
Joined: Mon Sep 18, 2017 5:08 am

Re: Gospel Library for Windows 10 Version 4.0.0.0

#40

Post by lcheesman »

I would like to download the scriptures that I have tagged for a specific subject- i.e. for the topic of "guilt" I would like to download to a Word document all the scriptures and references I have tagged under "guilt". I don't see how to easily do that. I could go to each scripture reference and copy and paste into a document, but that seems like too much work. Please enlighten me.
Post Reply

Return to “Gospel Library for Windows”