Web app requires Sign in when new version is available

Dave Hooton
Dave Hooton MVP Posts: 36,185
edited March 31 in Beta Desktop App Forum

I had been testing Verbum 41 B2 with Auth when both Logos.com and the Web app were in my Main account (Firefox browser):

  1. Changed Logos.com to Test account
  2. Test Verbum app
  3. Changed Logos.com back to Main
  4. More tests on Verbum app
    1. it takes several minutes
  5. Return to Web app and it states that a new version is available
    1. click the popup
    2. get a request to Sign in
    3. I can Authorize Main (so why was Sign In needed?)
    4. Get an error message with possible verification via Email!
    5. Click Authorize button again
    6. Web app now back to Main (was it ever NOT in Main?)

Similar testing using Steps 1 thru 4 shows that the Web app is still in Main at Step 5.

Dave
===

Windows 11 & Android 13

Tagged:

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,185

    @Adam Borries (Logos)

    I returned to my browser today in Desktop and found I had to sign -in to Logos Web App from the above session. No message.

    Please explain.

    Dave
    ===

    Windows 11 & Android 13

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

    All sites and APIs are allowed to "cache" local-cookie and OAuth-header validity for up to 5 minutes. Therefore, even after a successful "global sign out", you may still observe being "logged in" during that cache-busting period.

    There's not enough information here to provide a definitive explanation, but if the sign-out/sign-in dance between logos.com and app.logos.com all happened within that 5-minute cache period, it could have still treated you as signed in; but without actually validating the credentials, the cache would have expired by the time you came back the web app. (I don't know why it would have you verify your email; that seems like it might be a bug.)

  • Dave Hooton
    Dave Hooton MVP Posts: 36,185
    edited April 8
    https://community.logos.com/discussion/comment/1365476#Comment_1365476

    @Adam Borries (Logos) Did you respond to this post? Because I only had to re-Authorize the web app to Main after being left for 7 days.

    Dave
    ===

    Windows 11 & Android 13

  • Adam Borries (Logos)
    Adam Borries (Logos) Community Manager, Logos Employee Posts: 972
    https://community.logos.com/discussion/comment/1365594#Comment_1365594

    Yes. My response above was my explanation for that post.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,185

    OK…it seemed more oriented to my original post. So it would be expected that after 7 days I just saw a colorful screen with a Sign In box near the bottom after clicking its tab?

    Does the web app require a sign in when a new version is available?

    That seems to be negative as I just checked the app after leaving it alone for a day (in Main with logos.com). The ESV bible panel was empty and could not be encouraged to display a new passage. Factbook responded ok but then I glanced down and saw a little box in the bottom RH corner of my large monitor stating that I should refresh to get a new version, after which (no sign in needed) the bible returned to normal and the app was still in Main.

    I'll only say that something is not quite right with the web app and that a more visible notice to refresh would be appreciated.

    Dave
    ===

    Windows 11 & Android 13

Categories