Troubleshooting
Turn on debug logging
NiteaOptions.builder("examplemod")
// ...
.debug(true)
.build();
The log then shows every request and the server's response. Turn it off before releasing.
Log messages
| Log message | Fix |
|---|---|
No SDK key found, reporting is off. | Add your SDK key. Check the jar contains nitea/<modid>.properties. |
The SDK key should start with nt_ | The value isn't an SDK key. Copy it again or regenerate it. |
The Nitea API rejected the SDK key | The key was regenerated or the project deleted. Use the current key. |
Nothing is sent until the player allows Nitea reports | The player hasn't answered the consent screen, or on a server consent=granted isn't set. |
The player opted out of Nitea reports | The player chose Don't allow. They can change it from the title screen. |
Reporting for this mod is turned off in config/nitea/nitea.properties | Remove <modid>.enabled=false from that file. |
Could not reach https://nitea.cc/... | Network problem. The event is retried, then dropped. |
Still nothing in the dashboard
The version is ignored
Check the project's ignored versions. Events whose release matches exactly are dropped.
Player reports are turned off
Bug reports and suggestions are dropped when Accept player reports is off in the project's settings.
The error belongs to another mod
Uncaught exceptions and crashes are only reported by the mod whose code caused them. Check that owner(...) or inAppPackages(...) covers your packages. See Which mod gets the error.
The error was rate limited
At most 3 events a minute with the same signature are sent, and 30 a minute in total per mod.
Gradle can't find the dependency
Check the https://libraries.nitea.cc repository is declared and the coordinates are cc.nitea:nitea-<loader>-<minecraft>:<version>, with a loader and Minecraft version from the supported versions.