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

FetchError ECONNRESET often when running in background #48

Open
nightpool opened this issue Dec 31, 2022 · 5 comments
Open

FetchError ECONNRESET often when running in background #48

nightpool opened this issue Dec 31, 2022 · 5 comments

Comments

@nightpool
Copy link

I often get ECONNRESET fetch errors when running the presence monitor in the background, pictured below:

image

I also see this when using S3S, my guess is that this is due to rate limiting or server instability on Nintendo's part. I would say this happens every hour or two.

These errors are definitely pretty annoying, since they make an error noise popup and make my task bar pop up and flash orange every time they happen. Since they represent transient network issues, I would expect that they are handled and retried silently without interrupting the user.

@Phidica
Copy link

Phidica commented Jan 16, 2023

I've been getting this same error, in my case running on Linux. At times it will pop up multiple times within a span of just a few minutes. There's nothing a user can do about this, so it ought to be caught and handled silently.

Edit: Might be worth mentioning that I have two accounts connected, my main account and a secondary for Discord rich presence of the main. I have both of them set up to monitor their friends lists for desktop notifications.

@OctoFloofy
Copy link

trying the presence API for a while i can confirm. While using multiple accounts i didnt got errors as much.

@Nerdextrous
Copy link

I am also getting this.. any fix??

@nightpool
Copy link
Author

@Nerdextrous There's a fix in progress, looks like some commits were just pushed recently that made this better. Needs testing & a new release before those commits make it to end-users

@Nerdextrous
Copy link

@Nerdextrous There's a fix in progress, looks like some commits were just pushed recently that made this better. Needs testing & a new release before those commits make it to end-users

Awesome, thanks for the update! :)

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

No branches or pull requests

4 participants