No events arrive
The usual reasons an event doesn't show up, and how to tell which one it is.
Send one event with curl first (see the Quickstart). The answer tells you most of what's wrong.
| What you see | Why | What to do |
|---|---|---|
200 with "accepted":0 and a rejected list | Each line says why it was refused | Fix the field it names (see the common line errors). Never resend rejected lines. |
401 unknown or revoked key | The key is wrong, was revoked, or isn't a Lyrelog key | Copy the key again, or make a new one on API keys |
403 this key cannot write events | It's a Read events key | Use a Send events key (lyr_ing_) |
415 | Content-Type isn't application/x-ndjson | Set the header |
429 with plan, limit and used | The Free month is used up | The SDKs keep the events and send them when the month turns. See Plans and usage |
429 with source_limit | One address sent its share of the day with a public key | From a server, use a server key (lyr_srv_). Otherwise events resume the next UTC day. See the daily share of one address |
429 rate limit for this project | Over 60,000 events a minute | Wait for Retry-After |
425 with verification_required | The project accepts only verified events from that platform, and this batch isn't verified | The SDK keeps it and retries. Builds, simulators, emulators and devices that can't prove themselves never get through: turn the option off in Project settings while they matter. See Verified events |
503 | The server is busy or can't reach its storage for a moment | Retry the same bytes after Retry-After (the SDKs do) |
A 3xx | The endpoint is wrong | Use https://ingest.lyrelog.com |
| Accepted, but not in the dashboard | The dashboard shows one environment: builds you run from Xcode, the simulator, Android debug builds, localhost and Node without NODE_ENV=production send development | Pick development or All environments in the top bar, and All platforms |
| Accepted, but at the wrong time | The ts was older than the retention or more than a day ahead, so it was stored at its arrival time | Look at the attribute _lyrelog_ts_clamped, and send the current time |
| Nothing at all from a Swift app | The SDK sends nothing while consent is .pending or .denied | See Consent |
| Nothing at all from an Android app | The SDK sends nothing while consent is PENDING or DENIED, or the endpoint isn't one it accepts | See Consent and In development and tests |
| Nothing at all from a React Native or Flutter app | Consent is pending or denied, the endpoint isn't one the native SDK accepts, or the app wasn't rebuilt after adding the package | See Consent for React Native and Flutter, and Flutter's In development and tests |
| Nothing at all from a JVM server | The key is empty (start returns false and does nothing), or the process ended before the shutdown hook could send | See Start and Flush and stop |
| Events from your server in the wrong country | The country is the sender's address | See Countries |
What the SDKs say
Each SDK reports its own problems (a wrong endpoint, a refused key, a dropped batch) without crashing your app:
| SDK | Where to look |
|---|---|
| Swift | The unified log, subsystem com.lyrelog.sdk: Console.app or Xcode's console |
| Android | Logcat, tag Lyrelog, at debug level |
| React Native | The native SDK's log: the unified log on iOS (Xcode's console), logcat on Android, as above. A missing key or native module is one console.warn in development builds, in Metro |
| Flutter | The native SDK's log: the unified log on iOS (Xcode's console), logcat on Android, as above. mirrorToConsole: true also prints every event there |
| JavaScript | console.warn lines starting with [lyrelog] |
| Python | The lyrelog logger (standard logging) |
| Go | Config.ErrorLog, else the first problem once on stderr |
| JVM | Standard error, lines starting with lyrelog: , once per process, or Configuration.diagnostics |
Still stuck?
Write to hello@lyrelog.com with the project id (in Project settings, Details) and the time you sent the event. Never send a key.