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.

Sign up for GitHub

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

Jump to bottom

Switching games doesn't work/takes a long time to update #3

Closed
MCMi460 opened this issue Mar 29, 2022 · 1 comment
Closed

Switching games doesn't work/takes a long time to update #3

MCMi460 opened this issue Mar 29, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@MCMi460
Copy link
Owner

MCMi460 commented Mar 29, 2022

This is a common bug in the current version (tag v1.0) of the app.

It is not limited to any specific operating system, nor is it limited to the GUI.
However, it is only partially a bug. The current minimum update time of the app is 55 seconds (save for some manual conditions). This issue, instead, a feature request for shorter times.

Some caveats to this:

  • Heavier 3rd-party API usage
  • Possibly more suspicious API calls to Nintendo

The goal of this issue is to accomplish adding shorter refresh times without any/most of the disadvantages.
@MCMi460 MCMi460 added the enhancement New feature or request label Mar 29, 2022
@MCMi460 MCMi460 changed the title Switching games don't work/take a long time to update Switching games doesn't work/takes a long time to update Mar 29, 2022
@MCMi460 MCMi460 mentioned this issue Mar 29, 2022
Closed
MCMi460 added a commit that referenced this issue Mar 30, 2022
@MCMi460
Lower heavy usage of 3rd-party API (#3)
d85286d 
(Sorry again, @frozenpandaman!)
This commit should make each ping to the `s2s` and `flapg` APIs an hour apart. It also speeds up update time as it shouldn't be as risky with an API call other than `/v3/Account/Login`
@MCMi460
Copy link
Owner Author

MCMi460 commented Mar 30, 2022 •
edited
Loading

This should be mostly fixed now. Both of the caveats seem to be avoided by using /v3/User/ShowSelf method instead of constantly logging in and regenerating an f token like I used to.
Thanks to @samuelthomas2774 for the suggestion. Check out his Github repositories, as well!

Edit: Forgot to mention that this is fixed as of tag v1.1

@MCMi460 MCMi460 closed this as completed Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MCMi460