Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes when linking account then throws out error when reopening program #165

Open
wreaver opened this issue Nov 22, 2024 · 6 comments
Open

Comments

@wreaver
Copy link

wreaver commented Nov 22, 2024

Have tried 2 different accounts already and deleting the NSO-RPC folder on My Documents, but it always throws out the same result:

  1. Link account to NSO-RPC, program crashes.
  2. Reopen program, throws out error and closes until NSO-RPC folder is deleted.
  3. Repeat

This is the error in question:
Traceback (most recent call last):
File "cli.py", line 90, in update
File "api_init_.py", line 201, in getSelf
KeyError: 'result'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "app.py", line 836, in
File "app.py", line 342, in selfService
File "app.py", line 481, in changeState
File "app.py", line 478, in changeState
File "cli.py", line 95, in update
Exception: Cannot get session token properly

@MerakiMage
Copy link

I'm running into the exact same issues; My log.txt looks like this:

1732296935.437522: Successfully Connected to Discord.
1732296935.437522: Failure with authorization: 'result'\Friends returns {"status": 9406, "errorMessage": "Unauthorized.", "correlationId": "eac1a088-ec65e7d6"}
1732296935.437522: 'result'
1732296935.437522: Login from imink
1732296935.437522: 'result'
1732296935.437522: Cannot get session token properly
1732296988.727187: Successfully Connected to Discord.
1732296988.727187: Failure with authorization: 'result'\Friends returns {"status": 9406, "errorMessage": "Unauthorized.", "correlationId": "2e138923-e381c1ae"}
1732296988.727187: 'result'
1732296988.727187: Login from file
1732296988.727187: 'result'
1732296988.727187: Cannot get session token properly

@HotaruBlaze
Copy link
Contributor

HotaruBlaze commented Nov 22, 2024

Yeah we're aware of the issue, its been reported in the discord and its being looked into.

We know what broke but a fix is currently unknown.

Edit: For more context for people who want to know, Nintendo changed something their side and broke it.
See Below for an update

This was referenced Nov 30, 2024
This was referenced Dec 9, 2024
@HotaruBlaze
Copy link
Contributor

Nintendo has recently updated Nintendo Switch Online (NSO), breaking support for all third-party tools. Apps like s3s, nxapi, NSO-RPC and others are currently not working.

Updating authentication credentials isn’t possible at the moment, and these services may remain unusable.

Theirs currently no ETA for a fix.

@Yeetov
Copy link

Yeetov commented Dec 15, 2024

Sad :(

@luni-moon
Copy link

Nintendo has recently updated Nintendo Switch Online (NSO), breaking support for all third-party tools. Apps like s3s, nxapi, NSO-RPC and others are currently not working.

Updating authentication credentials isn’t possible at the moment, and these services may remain unusable.

Theirs currently no ETA for a fix.

It may be a good idea to make a new issue or smth and pin this, as it seems a lot will be asking what's going on, as was I, but skimmed the other issues before doing so. I kinda figured they updated their API in some way.

@HotaruBlaze
Copy link
Contributor

Nintendo has recently updated Nintendo Switch Online (NSO), breaking support for all third-party tools. Apps like s3s, nxapi, NSO-RPC and others are currently not working.
Updating authentication credentials isn’t possible at the moment, and these services may remain unusable.
Theirs currently no ETA for a fix.

It may be a good idea to make a new issue or smth and pin this, as it seems a lot will be asking what's going on, as was I, but skimmed the other issues before doing so. I kinda figured they updated their API in some way.

Once this PR is merged #169, Their will be a disclamer in the readme at the top telling people its broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants