[steam deck] Javascript Error and Console not showing up

Question

[steam deck] Javascript Error and Console not showing up

Closed this issue 9 months ago · 27 comments

Hey, I installed Greenlight 2.0 as shown in the tutorials and logged in with my Xbox Account, but my Xbox isn't showing up and i get the following error:

A JavaScript error occurred in the main process

Uncaught Exception:
TypeError: Cannot read properties of undefined (reading
"getProvider")
at IpcMainimpl. (/tmp/.mount_GreeniuuPxCp/ resources/app.asar/app/background.js: 1:72232)
at IpcMainimpl.emit (node events:390:28)
at Eventemitter, «anonymous» (node electron/js2c/browser_ init
161:10780)
at Eventtmitteremit (node events 390:28)

I already reinstalled Greenlight and also deleted the config files.
Any thoughts or suggestions would be appreciated. :)

Answer 1 · 2022-10-27T21:18:54.000Z

Having the same issue all of a sudden it was working fine a week ago

Answer 2 · 2022-10-28T07:30:47.000Z

Also noticed that the Login Screen doesn't disappear on it's own. The Login Screen stays open and shows nothing, it's just white.

Have tried out 1.2 yesterday and on the first start it worked, I could login and connect to my console but after I closed and reopend 1.2 the same thing happend. Same Error and I was logged out.

Answer 3 · 2022-10-29T14:52:22.000Z

Same issue here on the latest version v2.0.0-beta1 ☹️.

Answer 4 · 2022-10-30T18:38:20.000Z

I have a similar issue on the latest stable v1.2.0. The difference is I get a type error reading "url" instead of "getProvider"

The deck refuses to upload generic screenshots, unfortunately.

If I delete Home/.config/xbox xcloud I'm able to login with my credentials again and start up my Xbox remotely. However the next time I quit the program I'm presented with the same JS error.

Answer 5 · 2022-11-05T02:10:50.000Z

As mentioned previously I have had the issue my xbox not appearing but double check your xbox mine had some how deactivated remote play.

It wasn't of my doing perhaps it happened on an update

Answer 6 · 2022-11-05T10:15:17.000Z

I have a similar issue as well, only the parameters of the error are different, on 2.0.0-beta2.

Answer 7 · 2022-11-05T10:57:52.000Z

As mentioned previously I have had the issue my xbox not appearing but double check your xbox mine had some how deactivated remote play.

It wasn't of my doing perhaps it happened on an update

Checked mine and remote is activated, so have be something different.

Answer 8 · 2022-11-05T11:31:40.000Z

I have a similar issue as well, only the parameters of the error are different, on 2.0.0-beta2.

So inspecting a bit deeper the issue, I would like to report the following:

The Java error occurs both on my Steam Deck and my M1 Macbook Pro.
On both platforms, the bug is not critical; after I click OK on the error, I can proceed with the remote play as usual, ΧBOS shows up and it works perfectly.

Answer 9 · 2022-11-05T21:32:04.000Z

I started having this issue on 2.0.0-beta1 running on Steam Deck and am still having it on beta2. In both versions, I can get it to work eventually by restarting Greenlight until I can get to its settings then logging out and back into my Xbox account using Greenlight. It takes a few tries usually. After a successful play session, I'll usually have to repeat this process next time I play.

Answer 10 · 2022-11-13T23:19:21.000Z

I haven't changed what version I'm using since my last comment, v1.2.0.

I tried going into desktop mode on my Steam Deck and while I still get the Javascript error I'm able to close the popup, try again, and manage to proceed connecting to my Xbox.

Answer 11 · 2022-11-22T15:54:40.000Z

Same. Happen rate is like 70%. 2.0.0b2

TypeError: Cannot read properties of undefined (reading "getProvider")

Answer 12 · 2022-12-27T17:52:30.000Z

I've been having better luck with 2.0.0-beta2 so far. I've only tried launching it 3 times in the same day, but it worked each time from within SteamOS. An added side benefit is my game no longer lags after ~10 minutes of playing. I was able to play for hours without any signs of delay.

Answer 13 · 2022-12-27T18:04:51.000Z

It was bad a month ago on 2.0.0-beta2 but has been much better in the last couple weeks. So, this may have been due to some issue that got fixed on Microsoft's end because this app has not been updated since then.

Answer 14 · 2023-02-11T00:08:15.000Z

Please try the new 2.0.0-beta3 release. I could not reproduce the error on the new version.

Answer 15 · 2023-02-28T01:06:09.000Z

Still receiving on latest version. beta3

Answer 16 · 2023-03-11T12:04:58.000Z

This is still unresolved as of the latest release beta4.

Answer 17 · 2023-05-04T00:46:00.000Z

A workaround solution on the Steam Deck is to go to Properties (while in Gaming mode) and set Compatibility to Force Use of Specific Version of Proton option (checkmaek). Restart the app and it will crash back to Library screen after attempting to load. Go back to Properties and undo the change you made to Compatibility (uncheck it). Should be good to go for a while.

Answer 18 · 2023-09-21T09:52:02.000Z

Hey, it has been a while. Is the issue still happening with the latest version?

Answer 19 · 2023-09-23T01:08:07.000Z

Hey thanks for checking - I haven’t had it happen for a while after I reported the workaround, but I have also not played as much or updated the version. Will keep you posted, ty

…

On Thu, Sep 21, 2023 at 5:52 AM UnknownSKL ***@***.***> wrote: Hey, it has been a while. Is the issue still happening with the latest version? — Reply to this email directly, view it on GitHub <#510 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7TDEISAJQRIOTCU5MPIV4DX3QE47ANCNFSM6AAAAAARP2MN5I> . You are receiving this because you commented.Message ID: ***@***.***>

Answer 20 · 2023-09-28T13:24:45.000Z

Hey, it has been a while. Is the issue still happening with the latest version?

I'm still having the problem and it doesn't allow me to log in and I'm left with a white screen with the latest version. Now in case I'll try version 1.2.0 and see if the problem goes away.

Answer 21 · 2023-09-28T13:24:52.000Z

Hey, it has been a while. Is the issue still happening with the latest version?

I'm still having the problem and it doesn't allow me to log in and I'm left with a white screen with the latest version. Now in case I'll try version 1.2.0 and see if the problem goes away.

Answer 22 · 2023-09-29T00:20:25.000Z

White authentication screen of death I resolve by doing the same (forcing specific so it fails to launch 1-2 times, then unchecking as it was) while in Desktop Mode (takes a bit to load sometimes). I just did it now to resolve it, using whatever version this thread is on (I never updated). Best of luck!

…

On Thu, Sep 28, 2023 at 9:25 AM greensciuto ***@***.***> wrote: Hey, it has been a while. Is the issue still happening with the latest version? I'm still having the problem and it doesn't allow me to log in and I'm left with a white screen with the latest version. Now in case I'll try version 1.2.0 and see if the problem goes away. — Reply to this email directly, view it on GitHub <#510 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7TDEIWGIS6P72LVHGBQMBDX4V3DDANCNFSM6AAAAAARP2MN5I> . You are receiving this because you commented.Message ID: ***@***.***>

Answer 23 · 2023-09-29T00:34:41.000Z

I solved it(problem on another Arch Desktop, no problem on windows(beta14)) by compiling again from source(git main branch). 1.73 Beta Rust + yarn/npm from default pacman. Then use AppImage in resulting dist folder. On Sep 29, 2023 8:20 AM, thumpah ***@***.***> wrote: White authentication screen of death I resolve by doing the same (forcing specific so it fails to launch 1-2 times, then unchecking as it was) while in Desktop Mode (takes a bit to load sometimes). I just did it now to resolve it, using whatever version this thread is on (I never updated). Best of luck!

On Thu, Sep 28, 2023 at 9:25 AM greensciuto ***@***.***> wrote: Hey, it has been a while. Is the issue still happening with the latest version? I'm still having the problem and it doesn't allow me to log in and I'm left with a white screen with the latest version. Now in case I'll try version 1.2.0 and see if the problem goes away. — Reply to this email directly, view it on GitHub <#510 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7TDEIWGIS6P72LVHGBQMBDX4V3DDANCNFSM6AAAAAARP2MN5I> . You are receiving this because you commented.Message ID: ***@***.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

Answer 24 · 2023-09-29T00:37:40.000Z

Awesome! It seems my previous post only addresses it in Desktop mode; I’ll do as you did myself, thanks On Thu, Sep 28, 2023 at 8:34 PM Originalimoc ***@***.***> wrote:

…

I solved it(problem on another Linux client) by compiling again from source(git main branch). 1.73 Beta Rust + yarn/npm from default pacman.On Sep 29, 2023 8:20 AM, thumpah ***@***.***> wrote: White authentication screen of death I resolve by doing the same (forcing specific so it fails to launch 1-2 times, then unchecking as it was) while in Desktop Mode (takes a bit to load sometimes). I just did it now to resolve it, using whatever version this thread is on (I never updated). Best of luck! On Thu, Sep 28, 2023 at 9:25 AM greensciuto ***@***.***> wrote: > Hey, it has been a while. Is the issue still happening with the latest > version? > > I'm still having the problem and it doesn't allow me to log in and I'm > left with a white screen with the latest version. Now in case I'll try > version 1.2.0 and see if the problem goes away. > > — > Reply to this email directly, view it on GitHub > < #510 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A7TDEIWGIS6P72LVHGBQMBDX4V3DDANCNFSM6AAAAAARP2MN5I> > . > You are receiving this because you commented.Message ID: > ***@***.***> > —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#510 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7TDEIUT7WZBUCMCQBCGUJTX4YJS3ANCNFSM6AAAAAARP2MN5I> . You are receiving this because you commented.Message ID: ***@***.***>

Answer 25 · 2023-09-29T05:01:10.000Z

White authentication screen of death I resolve by doing the same (forcing
specific so it fails to launch 1-2 times, then unchecking as it was) while
in Desktop Mode (takes a bit to load sometimes). I just did it now to
resolve it, using whatever version this thread is on (I never updated).
Best of luck!

On Thu, Sep 28, 2023 at 9:25 AM greensciuto @.***>
wrote:

Hey, it has been a while. Is the issue still happening with the latest
version?

I'm still having the problem and it doesn't allow me to log in and I'm
left with a white screen with the latest version. Now in case I'll try
version 1.2.0 and see if the problem goes away.

—
Reply to this email directly, view it on GitHub
#510 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7TDEIWGIS6P72LVHGBQMBDX4V3DDANCNFSM6AAAAAARP2MN5I
.
You are receiving this because you commented.Message ID:
@.***>

I solved all the problems by downloading the beta 12 version of the latest version

Answer 26 · 2023-09-29T05:01:14.000Z

White authentication screen of death I resolve by doing the same (forcing
specific so it fails to launch 1-2 times, then unchecking as it was) while
in Desktop Mode (takes a bit to load sometimes). I just did it now to
resolve it, using whatever version this thread is on (I never updated).
Best of luck!

On Thu, Sep 28, 2023 at 9:25 AM greensciuto @.***>
wrote:

Hey, it has been a while. Is the issue still happening with the latest
version?

I'm still having the problem and it doesn't allow me to log in and I'm
left with a white screen with the latest version. Now in case I'll try
version 1.2.0 and see if the problem goes away.

—
Reply to this email directly, view it on GitHub
#510 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7TDEIWGIS6P72LVHGBQMBDX4V3DDANCNFSM6AAAAAARP2MN5I
.
You are receiving this because you commented.Message ID:
@.***>

I solved all the problems by downloading the beta 12 version of the latest version

Answer 27 · 2024-01-09T16:13:54.000Z

2.0.1 release should have fixed this problem. If the problem persists then please reopen the issue.