Automatic token generation is broken (9403: Invalid token.)

[frozenpandaman]

Nintendo put out a tweet regarding third-party tools (although s3s is not technically a smartphone app, ha!)

https://twitter.com/nintendo_cs/status/1661198043461603328

[Notice] We have confirmed the existence of smartphone apps that spoof legitimate apps for Splatoon 3 and other network services, and which fraudulently access our company's servers. Use of these types of apps may compromise your security and personal information, and there is a possibility of unexpected damage. Please be careful.

In conjunction, as of last night, the NSO app has also been updated to v2.5.1, and as of today servers have stopped accepting tokens generated by earlier versions. Despite updates to the imink API (and similar tools like nxapi-znca-api and nsotokengen) in attempt to rectify this, as is usually done when the NSO app updates, 9403 errors are still being returned, i.e. automatic token generation is currently broken.

Please follow the mitmproxy instructions to continue using s3s for the time being.

[niyari]

In the case of an error caused by an external factor, it seems necessary to display an easy-to-understand error message.
Specifically, display an explanation such as "Please wait a moment".
It seems necessary to rewrite a little depending on the error situation

[frozenpandaman]

@niyari Yep, I'm not sure how to best navigate this as it has the potential of lasting a while… in which case a better error message would be good. But I don't want to act too soon. I'll consider it further next week after waiting to see how things may have developed by then. In the meantime, I hope people will know to check here (or tweet at me, etc.) if they're looking for more info. 😉

[Coxxs]

I believe they have been preparing this since at least March (when 2.5.0 was released), the "check" for unofficial apps has been added since then.
A temporary fix: https://github.com/Coxxs/NSOk

[frozenpandaman]

samuelthomas2774/nxapi#10 (comment)

Changes have been summarized (publicly) here. s3s will be updated shortly when support for the new necessary parameters are added to the imink API.

[niyari]

s3s is now available again.

[beanjamin25]

im getting the following error now, which is obviously not an issue with s3s directly...

s3s v0.4.0
Validating your tokens...

The stored tokens have expired.
Attempting to generate new gtoken and bulletToken...
Couldn't connect to f generation API (https://api.imink.app/f). Please try again.

[frozenpandaman]

This token generation issue – by which I mean both the ability to successfully generate valid f tokens and the required reliability of being able to do that consistently – has not yet been resolved, which is why this GitHub issue is still open. The imink API has indeed been updated but the server is not fully stable, as you can see (nb: please do not flood it with further requests). Additionally, I have not yet added the new request parameters (which will likely be strictly required in the future) into s3s/iksm.py. I'm going to continue to suggest obtaining your tokens manually until this is actually fully fixed & specified as such here.

[frozenpandaman]

This should be resolved now!

[frozenpandaman]

@SicariusREAL As multiple people have pointed out to you before, this is not an s3s error.

spacemeowx2/s3si.ts#69