Beta 10 - stuck on "we are getrting your stream ready"

[trebs24]

Updated to 10, was on 2 until I had other issues. Now I can authenticate but when launching it gets stuck at "Loading... We are getting your stream ready"

Is this a bug with this version? I updated from 2 to 10, on steam deck.

[jshessen]

Merging this comment from #895 as duplicate

Using Beta 10 -- after logging out, and clearing data, the following is written to the command prompt after attempting login:

$ ./Greenlight-2.0.0-beta10.AppImage 
/tmp/.mount_GreenlGSGnlz/resources/app.asar/app/background.js[constructor()] Starting Greenlight v2.0.0-beta10
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: Error("EOF while parsing a value", line: 1, column: 0) }', src/rs_xal_authenticator.rs:236:28
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
(node:483396) UnhandledPromiseRejectionWarning: Error: sending on a closed channel
    at XalAuthenticator.close (/tmp/.mount_GreenlGSGnlz/resources/app.asar/app/background.js:1:682)
    at BrowserWindow.<anonymous> (/tmp/.mount_GreenlGSGnlz/resources/app.asar/app/background.js:1:98890)
    at BrowserWindow.emit (node:events:539:35)
    at /tmp/.mount_GreenlGSGnlz/resources/app.asar/app/background.js:1:100403
(Use `greenlight --trace-warnings ...` to show where the warning was created)
(node:483396) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

After terminating the command and relaunching, it progresses past the login, but hangs in the "We are getting your stream ready..."

$ ./Greenlight-2.0.0-beta10.AppImage 
/tmp/.mount_GreenlqVpknC/resources/app.asar/app/background.js[constructor()] Starting Greenlight v2.0.0-beta10
events.ts: Retrieved xuid: { xuid: '2801346196799550', state: 'Offline', cloaked: true }
Error fetching consoles. Status: 401 Body: 
(node:483612) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'code')
    at /tmp/.mount_GreenlqVpknC/resources/app.asar/app/background.js:1:91980
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use `greenlight --trace-warnings ...` to show where the warning was created)
(node:483612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

`

[cg-]

I'm also having these issues on beta 9 and 10 on a steamdeck.

[thejae]

Having the same issue but downgraded to beta 7, which still works.

On Mac OS Ventura 13.4.1

[jshessen]

Having the same issue but downgraded to beta 7, which still works.

On Mac OS Ventura 13.4.1

Just an FYI -- I am also able to work in Beta 8

[unknownskl]

There has been reports of increased waiting times on xCloud. Currently Greenlight cannot show the waiting times but it should connect eventually.

[cg-]

There has been reports of increased waiting times on xCloud. Currently Greenlight cannot show the waiting times but it should connect eventually.

To note, I'm having these issues on in home streaming. I've left it for several minutes before without success, but if I close the app and reopen it, sometimes it will work.

[jshessen]

There has been reports of increased waiting times on xCloud. Currently Greenlight cannot show the waiting times but it should connect eventually.

I think this is fair, but just to add context and color. At any time that Beta 10 is "hanging", I can connect with Beta 8 with no delay (immediately).

[gh0sti]

downgraded from b10 to b8 and can stream again

[Kobi-Blade]

Can confirm this affects remote play and is not exclusive to xCloud, beta 8 the connection is instant, beta 9 and 10 is constantly connecting until it errors.

[johnmurphy01]

Tried beta 10, 8 and 6 and none work for me. I'm using a Macbook Pro M1 running Ventura 13. Can login fine and it says Connecting to console and powers on the Xbox from standby. But it never connects. I don't think it's an issue with this particular repo, more of an issue maybe with with the xbox-xcloud-player package. Is any work being done to resolve this?

[m4tsu999]

Same for me. Tried different betas, all on Macbook Pro M1 (Ventura 13.5), remotly via Wifi or 5G (not inside Local Network). Keeps showing "getting stream ready". Xcloud seems to have no issues.

[jshessen]

Just noting updated testing. I noticed Beta 11 was released, and gave it a go (AppImage on Linux)

The "We are getting your stream ready..." issue persists.

/tmp/.mount_GreenlCrMAhS/resources/app.asar/app/background.js[constructor()] Starting Greenlight v2.0.0-beta11
events.ts: Retrieved xuid: { xuid: '2801346196799550', state: 'Offline', cloaked: true }
Error fetching consoles. Status: 401 Body: 
(node:201057) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'code')
    at /tmp/.mount_GreenlCrMAhS/resources/app.asar/app/background.js:1:93016
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use `greenlight --trace-warnings ...` to show where the warning was created)
(node:201057) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

[johnmurphy01]

I saw this too but even if I handle that error it's still not working. Seems like the connectionState event coming from the xcloud player isn't transmitting the connected state. The last state I get is connecting always.

[johnmurphy01]

More info, it seems that this logic: https://github.com/unknownskl/xbox-xcloud-player/blob/main/src/Library.ts#L257 isn't being executed. It's confusing because the console output at the entry point of this function isn't being triggered for audio and video yet the VideoComponent has console output that is being executed.

[Jayian1890]

Clicking on the Xbox logo to exit the app, then reopening seems to work for me. Maybe an incorrect closeure/cleanup?

[johnmurphy01]

Clicking on the Xbox logo to exit the app, then reopening seems to work for me. Maybe an incorrect closeure/cleanup?

That doesn't appear to work for me. It still seems like there's some event that isn't being emitted and so it stays in the connecting state.

[unknownskl]

Thanks for the info. I don't have the issue on my side which makes it really difficult to reproduce, however I ran into it once on the steam deck yesterday (reconnecting worked for me). Any pointers would be handy to have. In meantime I will check the suggestions in this post.

[Stealthieone]

I get this error when it just hangs at getting stream. I hope this helps (on beta 11)

[Kobi-Blade]

Thanks for the info. I don't have the issue on my side which makes it really difficult to reproduce, however I ran into it once on the steam deck yesterday (reconnecting worked for me). Any pointers would be handy to have. In meantime I will check the suggestions in this post.

I only got it working when I open a game on Xbox, if my Xbox is on Dashboard, GreenLight is unable to connect at all, even if I restart both GreenLight and Xbox.

This happens since Beta 9, all the way to latest release.

[jshessen]

Tested Beta 12 today -- went a step further just to add some detail.

If I force a log out I was able to successfully launch a title on 9-12 via "xCloud Library".

All versions (9/10/11/12) exhibit the same behavior (referenced above) when attempting to "Start Stream" directly to my console.

PS -- The update notification when launching previous versions is a welcome addition.

[ahkdigital]

My experience (different scenario) was that I could stream on Beta 8 but I downloaded Beta 12 today and it would not work.

What I decided to focus on was that the logged in user was carrying over between AppImages. That makes sense but I figured I would try doing the login process again in the newer one (i.e: in Beta 12, log out from Settings and then log in again) to see if it made a difference.

Yep, after logging in again then I was able to successfully start a stream on Beta 12. You (OP) mentioned that you upgraded from a previous one - so maybe trying logging out in the newest beta and then logging in again.

---

EDIT: Well, perhaps I spoke too soon. Now I'm still getting issues on Beta 12 ("We are getting your stream ready") but I can do the xCloud streaming. Beta 8 still works for console streaming.

[Stealthieone]

Confirmed beta 8 does not have this problem

[Stealthieone]

Spoke too soon beta 8 is giving me this problem. I've tried everything and if in standby I can't connect

[Stealthieone]

I think I might have figured out the problem.. In power options on Xbox you can customize your active hours.. I thought that was for the power save option and not the sleep option. I think even if you have your Xbox sleep if you set active hours then remote play will not work outside of those hours. I now have it set to always active and now remote play connects every time

[cart-su]

I've attempted this, that is, changing the active hours, but I'm still encountering the issue.

[unknownskl]

Problem has been identified and will be released with the next beta version :) It turned out to be an timing issue while retrieving the tokens.

[cart-su]

Should the commit referenced above resolve the issue, or is there more work to be done? I built the code with that commit, but still am encountering the problem.

[unknownskl]

The above commit should fix the code error in the console. It was thrown when there is no token found. Do you receive the same error with the new build?

[cart-su]

Yes, what seems to be happening is that it'll connect for a while (more reliably than before), but if I disconnect after a session and wait a little while, I can no longer re-connect until I remove power (unplug) the Xbox and plug it back in. After which case it'll connect that time, but the cycle will continue. I'm using a wired ethernet connection on the Xbox, and Wi-Fi on the MacBook. It may be something to do with the Xbox going to sleep, but I'm not sure.

[unknownskl]

https://github.com/unknownskl/greenlight/actions/runs/6150587434 (Check below 'Artifacts') Made a quick build in between the releases. Does this version work? I havent encountered any issues on my side anymore.