Gospel Library for Windows 10 Version 4.0.0.0

Discussions around the Gospel Library application for Windows for Desktop and Mobile
21bmedic
New Member
Posts: 1
Joined: Thu Oct 12, 2017 2:29 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby 21bmedic » Sun Apr 15, 2018 4:36 pm

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
Senior Member
Posts: 3819
Joined: Mon Sep 26, 2011 8:42 pm
Location: Provo, UT
Contact:

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby sbradshaw » Mon Apr 16, 2018 7:59 am

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 10:24 am

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby zORg_alex » Sat Jun 09, 2018 10:16 am

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: 3
Joined: Tue Feb 21, 2012 7:49 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby shawnsalisbury » Sun Aug 12, 2018 5:04 pm

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.

skittles2519
New Member
Posts: 9
Joined: Thu Apr 27, 2017 9:24 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby skittles2519 » Fri Aug 17, 2018 11:57 am

@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: 3
Joined: Tue Feb 21, 2012 7:49 pm

Re: Gospel Library for Windows 10 Version 4.0.0.0

Postby shawnsalisbury » Mon Aug 20, 2018 7:26 pm

4.2.4 fixed it, great thanks!!


Return to “Gospel Library for Windows”

Who is online

Users browsing this forum: No registered users and 0 guests