Releases: samuelthomas2774/nxapi-znca-api
Releases · samuelthomas2774/nxapi-znca-api
v1.5.0
- Add support for Coral 2.8.0
Full changelog: v1.4.0...v1.5.0
v1.4.0
- Add support for Coral 2.7.0
- Improve validation errors
- Issues that could cause generated tokens to be rejected by Nintendo's API will now always be included in a
warnings
property.
- Issues that could cause generated tokens to be rejected by Nintendo's API will now always be included in a
Full changelog: v1.3.0...v1.4.0
v1.3.0
- Add
na_id
andcoral_user_id
fields- These are used by Coral 2.4.0 and later, and must be set properly since 24/05/2023.
- If not provided the API will attempt to read the value from the token subject.
- Add
force-activity
andforce-service
start methods
Full changelog: v1.2.0...v1.3.0
v1.2.0
- Add
/api/znca/config
- This is compatible with the imink API's
/config
endpoint and can be used to fetch the latest version supported by the server. TheX-znca-Version
header must be sent to/api/znca/f
to make sure the same version is used.
- This is compatible with the imink API's
- Add per-user/hash method rate limit
- Remove forced version for older clients
- For nxapi-znca-api.fancy.org.uk, Traefik middleware is used to set the correct
X-znca-Version
header for older clients.
- For nxapi-znca-api.fancy.org.uk, Traefik middleware is used to set the correct
- Fix server exits when a device disconnects in multi-device mode
Full changelog: v1.1.1...v1.2.0
v1.1.1
- Use 2.5.0 for non-nxapi clients
- Fix using requested app version
Full changelog: v1.1.0...v1.1.1
v1.1.0
- Add support for connecting to multiple Android devices/containers in a single server process
- Add support for requesting a specific app platform/version
- The
X-znca-Platform
/X-znca-Version
headers should be used to indicate which version of the Nintendo Switch Online app the client will use.
- The
- Add metrics endpoint
- Remove token expiry check
- The Nintendo Switch Online app can send web service authentication requests with expired tokens.
Full changelog: v1.0.3...v1.1.0
v1.0.3
Full changelog: v1.0.2...v1.0.3
v1.0.2
- Update Frida to 16.0.7
- The frida-server binary on the Android device must also be updated to 16.0.7.
- Fix Docker entrypoint
Full changelog: v1.0.1...v1.0.2
v1.0.1
Full changelog: v1.0.0...v1.0.1
v1.0.0
Changes from nxapi 32475b7:
- Add
/health
- This endpoint returns the time the last
f
token was generated. - If an
f
token was not successfully generated in the last 30 seconds this will also attempt to generate one.
- This endpoint returns the time the last
- frida-server will not be restarted if it is already running
Changes from nxapi v1.4.0:
- Improve compatibility with the imink API in nxapi's f-generation server
- Added a
--start-method
option for setting how thef
-generation server starts the app on the connected Android device- The default is
service
, which attempts to start a background service to ensure an app process is running usingam
. - Setting this to
spawn
will use Frida to start a new app process even if the app was already running. - Setting this to
activity
will attempt to start the main activity usingam
. - This can now also be disabled entirely by setting this to
none
.
- The default is
- Added a
--adb-path
option to set the path to the ADB executable used by thef
-generation server - Added a
--adb-root
option to automatically restart adbd as root for thef
-generation server - Add server timing information to nxapi's f-generation server
- Hide Windows console windows when running ADB commands