BUG, Crash when adding a new note, V/L Beta 38.0.572

Bill
Bill Member Posts: 345 ✭✭✭
edited November 30 in Beta Desktop App Forum

Hopefully @Matt Mattox will see this.

In either logos or Verbum, open the Notes Tool, click New Note, Crash within a couple seconds.

I'm on Windows 11.

This happened before and I reported without a response from Logos a few weeks back before the current and a previous update, it somehow cleared up on it's own for awhile, but it is back.

I tried renaming the notes files and the notes tool manger files and restarted to force a new download of those to see if that would help but it did not resolve the problem.

My only work around is to create the note on my iPad Pro and then open it on my laptop pc and finish typing it. I have tremors so using a touch screen on the iPad is difficult.

Here are logs.

Verbum.zip

Too soon old. Too late smart.

Tagged:

Comments

  • Jack Caviness
    Jack Caviness MVP Posts: 13,514

    Logos 38.0.572 Mac OS 14.6.1 (23G93)

    I successfully created a new note without any problem on the Mac OS.

    Enable-and-Submit-Log-Files | Install 

  • Bill
    Bill Member Posts: 345 ✭✭✭
    https://community.logos.com/discussion/comment/1346597#Comment_1346597

    Agree, My iPad works fine too. This seems to be a Windows machine issue only, and possibly even just my machine problem IDK. But because it is Beta, normal Logos support won't touch it. I've already called them.

    Too soon old. Too late smart.

  • Adam Borries (Logos)
    Adam Borries (Logos) Community Manager, Logos Employee Posts: 881

    Thanks, Bill. 

    2024-11-30 09:54:46.6984 ERROR 21 ApplicationUtility | Unhandled exception in async work ServiceException: 'style' is invalid: 'highlight' of 'custom' requires 'markupStyle' to be set. (InvalidRequest)
   at Facility.Core.ServiceResult.Verify() in /_/src/Facility.Core/ServiceResult.cs:line 52
   at Facility.Core.ServiceResult`1.get_Value() in /_/src/Facility.Core/ServiceResult.cs:line 261
   at LDLS4.Panels.NotesTool.NotesToolViewModel.CreateNotes(AsyncMethodContext context, JToken args)

    This is another instance of the same error you were getting in this thread. This is an exceedingly rare crash ("lucky" you) that has something do with a custom highlight style that is no longer available.

    The bad news is, we don't know exactly how the app gets into this state, so it's hard for us to test a fix. The good news is, we do have a potential fix for it that will be coming out in v39 beta 1 next week. Let us know how it goes!

  • Bill
    Bill Member Posts: 345 ✭✭✭

    Thank you so much Adam!! That is fantastic service! I was beginning to worry that my problem was being overlooked.

    For what it's worth, I have deleted and added several custom highlights in the past six months ending mostly by September-October and this problem started after that.

    Too soon old. Too late smart.

  • Bill
    Bill Member Posts: 345 ✭✭✭

    The Beta 39 fix worked! Everything is back to normal.

    Thank you again Adam and team Logos!

    Too soon old. Too late smart.

  • Adam Borries (Logos)
    Adam Borries (Logos) Community Manager, Logos Employee Posts: 881

    So glad to hear it!

Categories