AutoUpdate to Loginfiles after 3/14/2023 Patch Hangs Indefinitely

[Phdntom]

Describe the bug The autoupdate after the patch is permanently stuck with the message "Launchbuddy is updating Loginfile. This window should automatically close when the update is finished."

To Reproduce As of now, it occurs every time I try to play the game with Launchbuddy rendering the launcher unusable.

Expected behavior Per previous versions, launching should update each loginfile and then land on the main screen allowing account launch.

First happend in LB Version 3.2.4 on windows 11

Screenshots If applicable, add screenshots to help explain your problem.

[Phdntom]

[ATommasi]

Can confirm, happens to me as well

[PressedRat]

I am having the same problem.

[Wolfy339]

Same, and to add:

• Even if you log in manually, the small window stays around.
• If you cancel the update while inside the game, you get n error message about he log-in file.
• Sometimes after canceling/closing the game window, it attempts a second relaunch of the same account.

[rafo121]

Same problem for me.

[morpheus305]

Having the same problem. Sucks that it happened on a mystic forge day as well.

[ProfYakkington]

same here

[Stis]

I bet

Coherent UI has been replaced with Chromium Embedded Framework to power web-based interfaces like the launcher and Trading Post.

broke a lot of things...

[motorhead018]

Can confirm as well. Also, the ability to create a new loginfile is broken as well.

[tentpeg]

ditto same results

[Phdntom]

I bet

Coherent UI has been replaced with Chromium Embedded Framework to power web-based interfaces like the launcher and Trading Post.

broke a lot of things...

I am not sure it's entirely related to this. I was able to run an older version of Launchbuddy 2.4.1 and everything works as expected without even needing to recreate or modify the Loginfiles from the 3.2.4 version.

[WolfSabian]

After latest patch Launch buddy working properly now.

[motorhead018]

After latest patch Launch buddy working properly now.

This will only be temporary unfortunately. The Great GW2LB Creator will have to fix something in their code.

[Flapjakk]

After latest patch Launch buddy working properly now.

What do you mean latest patch?

My LB window still shows 3.2.4, but the problem suddenly stopped.

[ProfYakkington]

After latest patch Launch buddy working properly now.

What do you mean latest patch?

My LB window still shows 3.2.4, but the problem suddenly stopped.

New gw2 patch: " Chromium Embedded Framework has been temporarily removed and reverted to Coherent UI while we investigate a crash." - https://en-forum.guildwars2.com/topic/128855-game-update-notes-march-14-2023/#comment-1869692

[morpheus305]

Good thing they removed it cause now I can get daily mystic forger on the rest of my alts before reset

[Flapjakk]

After latest patch Launch buddy working properly now.

What do you mean latest patch? My LB window still shows 3.2.4, but the problem suddenly stopped.

New gw2 patch: " Chromium Embedded Framework has been temporarily removed and reverted to Coherent UI while we investigate a crash." - https://en-forum.guildwars2.com/topic/128855-game-update-notes-march-14-2023/#comment-1869692

Ah, thanks.

[Pekols]

AutoUpdate to Loginfiles after 4/18/2023 Patch Hangs Indefinitely again

[WolfSabian]

Chromium is back, and with it this issues has returned.

[Albacksen]

Yep. It's ferkacte now. Guess we have to wait for a patch for Launchbuddy.

[S7Ado]

u can also use https://github.com/TheCheatsrichter/Gw2_Launchbuddy/releases/tag/2.4.1 , it work's fine

[Wolfy339]

Just came to check/confirm that the issue is back!

[serenity44]

Confirming here as well. I opened GW2 on it's own and it updated just fine. Then opened launch buddy and hang. Even killing all of the attempts to update and just trying to make a new account or erasing an existing account and trying to remake results in me being able to login but LB does not recognize the game is running.

[TheWhiteWolves]

https://github.com/TheCheatsrichter/Gw2_Launchbuddy/blob/master/Gw2%20Launchbuddy/Modifiers/LocalDatManager.cs#L160

@TheCheatsrichter From a quick scan of what LB is doing, seems we are stuck in the loop here waiting for the prelogin state. hope that helps with tracking down the issue with whatever Anet changed. assume they modified whatever it is you use to work out the state of the UI

[She-Ra8315]

Same problem for me, today, whereas last patch for SAB worked fine for me, tho. I tried restarting my laptop, nothing. I got excited to see a new build again just now, but same eternal hang at the login screen, even after updating outside LB, then trying LB again.

[WolfSabian]

u can also use https://github.com/TheCheatsrichter/Gw2_Launchbuddy/releases/tag/2.4.1 , it work's fine

Oh man, as a current and hopeful means to get my accts online and multibox I'm attempting this. I'm currently reliving the pain of "Client XXXX got closed or crashed before a clean start" with every account

[Flapjakk]

u can also use https://github.com/TheCheatsrichter/Gw2_Launchbuddy/releases/tag/2.4.1 , it work's fine

This version triggers the old "login file for account name did not update correctly" error cascade. And I never remember whether continue yes or continue no is the option that breaks it less.

Edit: Got it mostly working. Closed and relaunched with minimum hassle, now most of the accounts are working no problem (one of them needed the credentials re-entered).

[rav550]

Which option breaks it less? I can't get 2.4.1 to work for me.

[Flapjakk]

I think "yes."

After yes-ing everything, I closed it entirely and relaunched. Had to go through the rigamarole of downloading everything again, but this time no error messages and only 1 broken account.

[rav550]

Thanks, seems to be working. I had to manually click close on the launcher window because it would just wait indefinitely, then select the 'yes' option in the launchbuddy dialog popup.

[TakuGW2]

Sadly is 2.4.1 not working for me either, idk why but the launcher just closes and no loginfile is created

[github-actions[bot]]

This issue is stale because it has been open 200 days with no activity. Remove stale label or comment or this will be closed in 7 days