search

Yellow-Dog-Man / Resonite-Issues

Issue repository for Resonite.
https://resonite.com
102 stars 0 forks source link

Major updates log user out #1924

Closed jae1911 closed 1 week ago

jae1911 commented 2 weeks ago

Describe the bug?

When upgrading to a new major update (non-compatible with previous), I get logged out of the game on the first start and have re-login.

The "remember me for 30 days" was checked on last login.

Some settings such as audio interfaces also get reset.

To Reproduce

  1. Log into Resonite
  2. Wait for major update
  3. Upgrade
  4. Start game
  5. Logged out on game start

Expected behaviour

I should stay logged in.

Screenshots

Resonite_1MuEwjxwy9

Resonite Version Number

2024.5.3.467

What Platforms does this occur on?

Windows

What headset if any do you use?

Index; Desktop

Log Files

TETHYS - 2024.5.3.467 - 2024-05-03 11_29_56.log

Additional Context

No response

Reporters

U-j4 | j4.lc (Discord)

ohzee00 commented 2 weeks ago

DESKTOP-V75BHJO - 2024.5.3.467 - 2024-05-03 04_06_40.log Here is my log of the exact same thing happening, reproducing this is really difficult given it happens only on updates but it has been consistent these past few days with a update.

Readun commented 2 weeks ago

It interestingly only startef since the update before the current one (haven't checked yet if the new update with Texture resolution will do that too)

Maybe we can pinpoint on when it started to happen?

Frooxius commented 2 weeks ago

Can you share the log from session immediately before the one that logged you out?

jae1911 commented 2 weeks ago

Can you share the log from session immediately before the one that logged you out?

Here is the log file for the session right before being logged out. Some notes:

Hosted to avoid GitHub's limit: https://bm.777.tf/TETHYS%20-%202024.5.1.68%20-%202024-05-02%2017_32_59.log

Frooxius commented 2 weeks ago

Thanks! One thing I see that is likely culprit there - UID calculation has failed in the last build before this one, which meant it computed it by fallback method, which results in a different UID. In the latest log, your UID is calculated normally.

We use UID to make sure that your login is only usable from the same machine as last time. Since UID changed, the token is invalid.

I'm not sure why it failed in previous build, it looks like one of the assemblies failed to load that were needed for it. I don't know if that's result of a mod or something else got messed up, but it's likely why the log out happened.

We'll have to see if it happens again, I don't see anything immediately actionable.

Banane9 commented 2 weeks ago

Ah, and here I was wondering why I was randomly not logged in when launching Resonite yesterday

shadowpanther commented 2 weeks ago

I'm not sure why it failed in previous build, it looks like one of the assemblies failed to load that were needed for it. I don't know if that's result of a mod or something else got messed up, but it's likely why the log out happened.

I don't use any mods, but the same happened to me too.

gameboycjp commented 2 weeks ago

DESKTOP-3EE2DAL - 2024.5.3.561 - 2024-05-03 13_20_45.log No idea if more logs will help, but I'll hand mine over anyways. I don't use mods, so this log will be clean. I did not log back in during this run.

GrayBoltWolf commented 2 weeks ago

Same issue here, getting annoying to have to re-login every time there's an update

and there's like 3 updates a day sometimes

Frooxius commented 2 weeks ago

@GrayBoltWolf Did every single of the updates released in a day log you out? Are you able to share logs for these?

Generally if you have this happening, we'd need logs from the session immediately before being logged out and after, otherwise we can't really do anything with this.

There is nothing about the updates that would inherently cause to be logged out. In J4's case it was because a dependency library failed to load for some reason, which changed the UID and invalidated the token, but that seems more like a busted install or something.

GrayBoltWolf commented 2 weeks ago

@GrayBoltWolf Did every single of the updates released in a day log you out? Are you able to share logs for these?

Generally if you have this happening, we'd need logs from the session immediately before being logged out and after, otherwise we can't really do anything with this.

There is nothing about the updates that would inherently cause to be logged out. In J4's case it was because a dependency library failed to load for some reason, which changed the UID and invalidated the token, but that seems more like a busted install or something.

This has happened to myself and Ralinesh both, two times in the last week. I'll try to remember to save logs before launching.

Frooxius commented 1 week ago

@GrayBoltWolf I need more details to understand which builds is this affecting.

When you say it happened twice a week, is that with every single build released? Or it happened with two builds?

Without logs though, we won't be able to do much.

GrayBoltWolf commented 1 week ago

@GrayBoltWolf I need more details to understand which builds is this affecting.

When you say it happened twice a week, is that with every single build released? Or it happened with two builds?

Without logs though, we won't be able to do much.

The recent ones I can remember for sure are: 2024.5.1.68 and 2024.5.3.1229

Before 2024.5.1.68 logged me out: DESKTOP-KHSI045 - 2024.4.30.495 - 2024-04-30 20_51_22.log

When 2024.5.1.68 logged me out: DESKTOP-KHSI045 - 2024.5.1.68 - 2024-05-01 20_58_04.log

Before 2024.5.3.1229 logged me out and after I logged back in after 2024.5.1.68: DESKTOP-KHSI045 - 2024.5.1.68 - 2024-05-01 20_59_35.log

After 2024.5.3.1229 logged me out: DESKTOP-KHSI045 - 2024.5.3.1229 - 2024-05-03 22_07_50.log

ExoTheWicker commented 1 week ago

I've had the same issue after each update. (I'm currently gathering logs and will reply when I have them)

ExoTheWicker commented 1 week ago

I've had the same issue after each update. (I'm currently gathering logs and will reply when I have them)

I've included logs for sessions before and after updates in the event that something needs to be compared.

ExoTheWicker - logs.zip

Frooxius commented 1 week ago

This might be fixed in 2024.5.7.505

I'm not 100 % sure of what's making the library freak out sometimes, but it might've been due to a package collision. I'll close this for now, if it still keeps happening, we can reopen this.