· 21. April 2026
Client SDKs, error pages and an English interface
Bug got the client side it was missing: SDKs for React and React Native that catch crashes and show an error page instead of a blank screen, API keys for sending events, and an interface that now reads in English.
Added
- An SDK for React Native. First release of the React Native client, with an error boundary and a default error page in the box. It ships a native module for iOS, and needs react-native-svg alongside it.
- Error boundaries that show something useful. The React SDK wraps an app in an error provider and an error boundary: when a render fails, the user sees a default error page rather than nothing, and you can pass your own component in its place.
- API keys instead of project IDs. An SDK is initialized with an API key, and the backend derives the project from that key, so the payload no longer has to name the project it belongs to. Requests can also authenticate with an API key header.
- Filtering and pagination on list endpoints. Requests can narrow a list down and ask for one page at a time instead of everything at once.
- Stacktraces attached to Discord messages. The Discord webhook integration uploads the stacktrace as a file along with the notification, so the full trace lands in the channel.
- Warning and fatal error levels. Events can be reported at those two levels in addition to the ones already there.
Improved
- The interface is in English. Project settings, releases, issues and user settings were translated from German, dates included.
- Integrations belong to an organization. The integrations view asks which organization you mean and lists only that organization's integrations.
- The SDKs are published as Artim Stacktrace. The React and Python packages were renamed. Existing installs need the new package name and imports.
- Long names and long traces stay in their place. Project and page names in the header are truncated with the full name on hover, and stacktraces in event and issue detail no longer stretch their section wider than the page.
- The service watches itself. The server logs incoming requests, authentication and event processing, and catches unhandled exceptions through the SDK; the frontend reports its errors the same way.
- Documentation for both SDKs. The React SDK has a README covering installation, usage and its API, and the Python SDK shows how to install it as FastAPI middleware.
Fixed
- The React SDK sent events to a development endpoint by default and now points at the production server.
- Peer dependency ranges were wrong on both SDKs: the React SDK now declares React 19, and the React Native SDK matches React Native 0.81.5.
- Creating a project without a platform left the field empty; it now defaults to "unknown".
- Error handling and logging in the React Native native module were tightened up, so a failure inside it says what happened.