The latest features, improvements, and fixes across Shipbook's SDKs and platform.
Every request your Node.js server handles now records its path, the caller's IP address and user agent, and you can add your own facts, such as the tenant or the plan, with one extractor. They appear in the request's header in the Logbook, next to its route, status and duration.
Node.js 1.7.0
Node.js docs →Native mobile apps now open in one timeline with the Node.js requests they made, as browser and React Native apps already could. Add the Shipbook session header to the requests your app sends to your backend. Each backend request then appears inside the app session that made it, with its route, status, duration and logs.
iOS 2.1.0, Android 1.10.0, Flutter 1.1.0
Session linking guide →A browser or React Native session and the Node.js requests it made now open as one flow in the Logbook. Open a session that called your backend, click "View full flow", and read the app logs and the server logs together, in time order. Each backend request is its own block with its route, status, duration and logs, so you see what the user did, what the server answered, and where it went wrong, without matching timestamps across two apps. Setup is one line in your app: attach the Shipbook session header to the requests it sends to your backend.
Console 2.41.0, Server 2.48.0, Browser 1.2.0, React Native 1.2.0
Session linking guide →For Node.js apps, every number that used to count sessions now counts requests: the dashboard gauges and charts, release health, and the Loglytics error rates. An issue's rate is the share of requests that hit it, charts go down to the minute, and alerts fire on request volume, so a server handling thousands of requests a minute is measured the way you think about it.
Server 2.49.0, Console 2.41.0
Node.js docs →Every request your Node.js server handles is now its own block in the Logbook: the endpoint, its status, how long it took, and the logs it wrote. Requests that ran at the same time no longer blur together, and MCP calls and background job runs get the same view. If the process crashes or is stopped, the SDK sends what it has before it exits, so the last logs are never lost. Uploads are batched, so a busy server sends a few requests a second instead of one per error.
Node.js 1.6.0
Node.js docs →The new Releases page gives every version of your app a report card: how much of your traffic runs it right now, its crash-free rate, and the issues it introduced or brought back. Deploys appear as markers on the dashboard graphs, so when errors spike you can see at a glance whether a release caused it. Releases are detected automatically from your traffic — or reported with exact timing from your CI or GitHub releases — and your AI agent can read the same data over MCP.
Server 2.46.0, Console 2.38.0
The Node.js SDK now picks up your app's version from package.json on its own — no configuration needed. Sessions arrive tagged with the release they came from, so you can filter logs by version and spot exactly which release introduced a problem.
Node.js 1.3.0
Every recurring error now has a status: mark it Fixed or Ignored right from the issue page, and Shipbook remembers the version it was fixed on. If the issue shows up again in a newer release, you get a regression alert. Brand-new issues alert the moment they first appear — by email, Slack, or webhook, with the AI analysis attached. Ignored issues stop alerting and drop out of your health graphs, and your AI agent can filter issues by status over MCP too.
Server 2.45.0, Console 2.37.0
The Bridge dashboard now leads with the numbers that sum up your app's health: the percentage of sessions free of crashes, errors, and warnings — each with a week-long trend, overall and per version, so you can see at a glance whether your app is getting healthier or worse.
Server 2.45.0, Console 2.37.0
When the AI analysis proposes a code fix, one click turns it into a GitHub pull request — Shipbook creates the branch, commits the changes, and opens the PR for your team to review. You can also just ask Logchat to open it. And the analysis no longer waits for a connected repository: every Loglytics issue now gets an AI read of its logs, and alert lists show the analysis summary at a glance.
Server 2.44.0, Console 2.36.0
Connect your repository →Connect your GitHub repository and Shipbook’s AI stops guessing from logs alone. When an issue spikes, the alert arrives with the root cause, a link to the exact line in your code, and a ready-to-paste fix — even across multiple files. The same analysis runs on demand on any Loglytics issue, and Logchat now answers questions using your actual source code. Alert webhooks carry the full analysis too, so your automations and AI agents get the fix in structured form.
Server 2.43.0, Console 2.35.1
Connect your repository →Shipbook’s MCP integration can now hand your AI agent the alerts that fired — list all of an app’s recent alerts, or pull the exact one a webhook pointed to. The agent can then dig into that session’s logs and investigate what went wrong, without you wiring up anything extra.
Server 2.42.0
See how AI agents use Shipbook →Alerts can now trigger a webhook. When one fires, Shipbook POSTs it to any endpoint you choose — Slack, PagerDuty, or your own AI agent or automation. Paired with Shipbook’s MCP integration, an agent can then pick up the alert and investigate the session’s logs on its own. Set it up in the new Webhooks section of the console.
Server 2.41.0, Console 2.34.0
Webhooks docs →Dashboards and Loglytics now count activity by session for backend apps, just like mobile — so your Node.js and server-side stats reflect how the app was actually used.
Server 2.40.0, Console 2.33.0
The JavaScript SDK got a tuned-up core and an updated Node.js package, so logs are sent more efficiently across browser, React Native, and Node apps.
@shipbook/core 2.1.0, @shipbook/node 1.2.0
If an app key was wrong or an app was deleted, the SDK used to keep retrying against the server until the next restart. Now it stops cleanly, saving battery and network.
iOS 2.0.2, Android 1.9.1
We moved Shipbook to a new search-engine cluster with smarter routing, so log search, dashboards, and Loglytics stay fast even as your log volume keeps growing.
Server 2.38.0
Read how we did it →Pick a time window in one click — in the logbook, Loglytics, Bridge, and log search. Your selected range now stays in sync as you move between them, so you keep the same view while you investigate.
Console 2.31.0
Filters can now exclude values, not just match them, compare app versions with operators like greater-than, and search on more fields — OS version, OS name, language, and class name. It is much easier to zero in on exactly the logs you want.
Server 2.35.0, Console 2.29.0
New MCP Integration and OAuth Connections pages in the console let you connect AI assistants like Claude to your Shipbook logs — so an agent can investigate real issues using your production data, safely and with your permission.
Learn about AI / MCP →You can now plug in custom appenders on iOS to send logs wherever you need. The iOS SDK also moved to Swift Package Manager as the single, modern way to install.
iOS 2.0.0
iOS docs →Android now supports custom appenders, with faster file loading, cleaner shutdown, and modern internals built on Kotlin coroutines.
Android 1.9.0
Android docs →The Shipbook Flutter SDK reached its first stable release — remote logging, automatic crash and error capture, session tracking, screen tracking, and offline queuing, all in one package.
Flutter 1.0.0
Flutter docs →Upload your source maps to turn minified, hard-to-read stack traces back into real file names and line numbers — so crashes and errors point straight to the code that caused them.
Console 2.26.0
The JavaScript SDK is now split into focused packages so you only ship what you need — a shared core plus dedicated builds for the browser, React Native, and Node.js.
@shipbook/browser 1.1.0, @shipbook/react-native, @shipbook/node
Browser docs →