Changelog

SDK

A new look for the bug report

  • The Report a bug button and the report screens look like app.blipit.io now: calm greys, thin borders, 8 px corners and one clear Send button. On websites they still take your site's font and main colour. In apps they follow your app's main colour and light or dark mode.
  • Browser SDK 0.3.23 (sites using the script tag and Odoo get it without a change), Android 0.7.5, Swift 0.8.0, React Native 0.6.3 and Flutter 0.5.3. React Native and Flutter also take a new color option for the button and the Send button.

Blipit

A new look for the dashboard

  • The Overview has a project search (press /) and a grid or list view. Usage, Alerts from the last 3 days and Recent issues sit on the left; on the right, each project card shows its latest open issue, how many issues are open and when the last event arrived.
  • A workspace switcher at the top of the sidebar shows your workspace and its plan and lists every workspace you belong to. A project switcher in the top bar lets you find a project by name, open it or create one, and Add project is always one click away.
  • The sign-in and sign-up pages have a new dark design.

Blipit

Copy-ready prompts for your AI coding assistant

  • The install guides and the guides for logs, traces, login attempts, releases, heartbeats, webhooks, Shield, session replay and the bug report button now have Copy prompt buttons. Paste the prompt into Claude Code, Cursor or any AI coding assistant and it does the setup in your project, using only the steps and the code from the guide.
  • In app.blipit.io, under API keys, Install instructions, the same prompt comes with your public key and project id already filled in. The secret key is never part of a prompt.

SDK

The Report a bug button and form match your site

  • Browser SDK 0.3.22: the button and the report form now use your site's font and main colour on their own, so they look like part of your product. The colour is read from a CSS variable such as --primary or --brand, your primary button or your links, and is adjusted so text stays readable on light and dark pages.
  • To set them yourself, pass color and font in feedbackWidget; both now apply to the form as well as the button. Turn matching off with match: false, or with Match my site in Project settings, Bug report widget. Projects that already had a custom colour keep it. Sites using the script tag and Odoo get this without a change; with npm, update @blipit/browser.

Blipit

Blipit Shield, Attack detection and Weak spots: security on the Scale plan

  • Shield blocks the IP addresses and accounts behind brute force, credential stuffing, scanners and web attacks, right inside your app. You choose the response for each kind of attack (block, alert, email the owners or just watch) and how long a block lasts. Shield stays off until you turn it on, starts in a test mode that only logs what would have been blocked, and has an allowlist and login rate limits.
  • Attack detection now also spots account takeovers, sign-ins from a new country or from two places too far apart, every new admin grant and, with Shield on, scanners looking for exposed files and injection, cross-site scripting and path traversal attempts. Alerts go to your usual channels.
  • Weak spots checks the libraries your apps run against known vulnerabilities and shows the version that fixes each one, checks the domains you monitor for exposed files, leaked keys, old TLS and missing protections, and gives every project a security score with what to fix first. A weekly security email can be turned on in Settings.
  • Shield, Attack detection and Weak spots are part of the Scale plan. Shield works with the Node.js and Next.js SDKs and the Odoo module. Weak spots reads the package list from the Node.js, Next.js, Python, Ruby, PHP and Go SDKs, the blipit packages command, or the Odoo module.
  • Bug reports has a new full-width layout: a service desk summary (open reports, SLA met, median first reply and satisfaction), a status strip, filters that apply as you change them, compact rows, and a preview panel where you can reply, assign a report to yourself or send it to your tracker without leaving the list. Arrow keys and j/k move through the reports.
  • Shield and Weak spots are also in the Blipit mobile app: turn Shield on or off, change responses, lift blocks and check your security score from your phone.

SDK

Shield and package lists in the server SDKs

  • Node.js 0.4.0 and Next.js 0.5.0 enforce Shield inside your app: the IP addresses and accounts Blipit blocks get a 403 and login rate limits answer 429. The list is refreshed every 30 seconds and kept if Blipit cannot be reached, and every check runs in memory. Use Blipit.shield() with Express, Fastify or plain http, and withBlipitShield in Next.js middleware.
  • Node.js 0.4.0, Next.js 0.5.0, Python 0.4.0, Ruby 0.4.0, PHP 0.4.0 and Go v0.4.0 send your app's installed packages once after start, and again only when they change, so Weak spots can check them for known vulnerabilities. Only with the secret key; it can be turned off in the SDK options.
  • The CLI 0.2.0 adds blipit packages, which sends the versions from the lockfiles in a folder (npm, PyPI, Composer, RubyGems and Go).

Odoo module1.18.14

Shield in Odoo

  • With Shield on (Scale plan), IP addresses and accounts Blipit blocks get a 403 in Odoo, blocked sign-ins are refused, and login rate limits answer 429 with the time to wait.
  • The list is refreshed every 30 seconds in the background. If Blipit cannot be reached, Odoo keeps working as usual with the last list. Test mode and the allowlist are respected. Update from the Odoo Apps store and upgrade the module in Apps.

SDK0.3.1

Android and iOS SDK 0.3.1: find apps stuck on startup

  • An app that freezes on its splash or loading screen does not crash or throw an error, so it went unnoticed. Call Blipit.reportReady() when the first screen can be used. If the app has been in the foreground for 20 seconds without it, Blipit sends one warning for that launch and groups every such launch into one Stuck on startup issue, with the screen and the breadcrumbs that led there.
  • Time in the background is not counted. Change the deadline with startupDeadlineMs on Android or startupDeadline on iOS, or set it to 0 to turn the check off. Update to blipit-android v0.3.1 or blipit-swift 0.3.1.

SDK0.4.0

Find apps stuck on a screen or in a flow, on Android, iOS, React Native and Flutter

  • Some failures never crash: a sign-in that never comes back, a startup that never shows the first screen, a payment sheet that never returns. Call Blipit.reportReady() when your first screen has its data, and wrap flows like sign-in with startFlow, flowStep and endFlow. If they do not finish in time, Blipit opens a Stuck issue with the step it stopped at, the screen and the last 30 steps.
  • Only time on screen counts, and the time limits are set by Blipit, so nothing needs tuning in your app. On Android, system kills on screen (low memory, too much CPU or memory) are reported too. Turn it on with waitForReady in the SDK options; it is off by default.

SDK

Every Blipit SDK now runs on Blipit's own core

  • Android v0.5.0, Java v0.2.0, Swift 0.5.0, React Native 0.5.0, Flutter 0.4.0, Python 0.3.0, Ruby 0.3.0, PHP 0.3.0, Go v0.3.0 and .NET 0.2.0 are built on blipit-nuggets, Blipit's own core. None of them contains a third-party monitoring library any more, most have no dependencies at all, and events go straight to Blipit in its own format.
  • Crashes are written to disk before the app or process stops and sent on the next start, reports wait in an offline queue while the network is down, and a 429 pauses sending for as long as Blipit asks. Laravel, Symfony, Rails, Sidekiq, ASP.NET Core and net/http are built in, with no extra package.
  • Upgrading: most apps only bump the version. There is no DSN any more, so Blipit.dsn and its equivalents are removed; Python, Ruby and PHP no longer need the project id; capture calls return the event id as a string; the level, user and breadcrumb types are Blipit's own; and beforeSend receives the event in Blipit's format.
  • React Native and Flutter: uninstall the third-party monitoring package that earlier versions installed alongside, and its Expo config plugin. .NET: remove the extra ASP.NET Core package and its builder.WebHost line, because Init covers ASP.NET Core. Android: the replay mask tag is now blipit-mask.
  • Apps still on an older version keep reporting as before. Each platform's guide in the docs has the new install line and init code.

Blipit

One project per app and platform

  • Every project now has one platform: Android, iOS, React Native, Flutter, Web, Backend or Odoo. You choose it when you create the project, and it cannot be changed later. Releases, versions, crash rates and store builds differ per platform, so an iOS app and an Android app now need two projects with two keys.
  • Data from another platform is refused with a clear error that says which project to create. The Blipit SDKs show that error once in the developer console, Logcat or the Xcode console and stop sending to that key until the app restarts. Refused data does not count against your quota.
  • When data was refused in the last 7 days, the project page shows how many events came from which platform, with a button that creates the right project with its platform and name already filled in. Existing projects got the platform that sent most of their data.

Blipit

Alert history, an alert bell, and alert links that open the right workspace

  • Every alert Blipit sends is now kept under Alert history on the Alerts page: new issues and regressions, dependencies and server health, uptime, status pages, workflows, Odoo performance, SLAs, on-call incidents, bug reports and more. Each one shows the sentence from the email, the project, the time, the channels and how many people got it, and whether it is still active or has cleared. Filter by project, type or state.
  • A bell at the top of the sidebar counts the alerts since you last looked and opens the latest 10.
  • Links in alert emails now open the right workspace. If you are a member of several workspaces and the alert came from another one, Blipit switches to it instead of showing Not found.

Blipit

Server health groups serverless functions per platform

  • Apps on Vercel, AWS Lambda, Netlify and Azure Functions no longer list every function instance as its own server marked Not reporting. They are grouped into one row per platform with the number of instances seen and their memory.
  • CPU from a paused function is not meaningful, so it is left out, and serverless instances never raise high CPU, slow response or stopped reporting alerts.

SDK0.6.0

Report a bug from the screen it is on: shake, screenshot, two fingers or after a crash

  • A Report a bug button in the Profile menu only captured the Profile screen. Now people can report from the screen with the bug: shake the phone, take a normal screenshot and tap Report, or hold two fingers on the screen for a second. After a crash, the next launch asks what they were doing and links the report to the crash.
  • When the reporter is opened from your own menu, Which screen? lets the person pick the current screen or one of the last 3. Name screens in Compose, fragment and SwiftUI apps with Blipit.setScreen. The floating button can be shown to everyone or only to testers from the project settings.
  • Each trigger is off by default: turn on shakeToReport, screenshotToReport, twoFingerReport and reportAfterCrash in the SDK options. Blipit never reads the screenshot or the gallery, and no extra permission prompt is shown. Update to blipit-android v0.6.0, blipit-swift 0.6.0, React Native 0.6.0 or Flutter 0.5.0.

Odoo module1.18.13

A key from another platform's project stops the module

  • If the key in Odoo belongs to a Blipit project for another platform, such as Android or a website, Blipit refuses the data with a message saying which project to create. Odoo now writes that message to the log once and stops sending with that key until you change it. The Blipit screens in Odoo show the same message.

Blipit

New Products pages on blipit.io, with a short video for each product

  • The Products menu and the new Products pages show all 19 Blipit products in five groups: Monitor, Pulse, Respond, Fix and ship, and Support. Each product has its own page with what it does, the plan it is in, the stacks it works with and a link to its guide.
  • Each page plays a short video of the product in use. Tap full screen to watch it with sound and captions, and the next product starts by itself when one ends. The videos are also on the Blipit YouTube channel in the Blipit Products playlist.

SDK0.3.1

Node SDK 0.3.1: no false slow-response alerts on serverless

  • Apps on Vercel, AWS Lambda, Netlify and Azure Functions no longer raise false "responding slowly" alerts. A function is paused between requests, and that pause was counted as event-loop delay. The Node SDK now leaves event-loop delay out on serverless hosts.
  • Blipit already ignores this value from serverless apps on older SDK versions, so the alerts stopped for everyone. Update to 0.3.1 to stop sending it at all.

Odoo module1.18.11

Edit or delete your chatter messages on a bug report

  • When you edit a message you sent to the team from a bug report's chatter in Odoo, the team now sees the new text in Blipit, marked Edited. Delete the message and it is removed from Blipit too, with its files.
  • Only your own messages are sent. Log notes and the team's replies stay as they are.

Blipit

Product update emails, with a switch in Settings

  • Blipit now emails its users about new releases, videos and tutorials, in each account's language. Settings has a Product updates by email switch, and every email has a one-click Unsubscribe link. Either one turns it off for your account.

Odoo module1.18.12

My report cards line up

  • On My report in Odoo, the What you reported card and the Screenshots, videos and files card are now the same height.

SDK0.3.18

Browser SDK 0.3.18: readable labels and buttons in replays

  • Session replays now show field names, column headers, tabs, menus and buttons, so you can follow which screen and button the visitor used. Typed values, table cells, record names, headings, breadcrumbs and the chatter stay masked, so a field shows as Customer: ******. Also in Odoo.
  • Show labels and buttons in replays is on for every project and can be turned off in the project's Session replay panel to mask all text as before. data-blipit-mask always masks an element and data-blipit-unmask shows one you choose.

SDK0.3.0

Android SDK 0.3.0: session replay in Android apps

  • Session replay now works in Android apps, Huawei devices included: watch a masked video of the app's own screens with taps, screen changes and errors on the timeline, under Replays in the dashboard. iOS, React Native and Flutter are coming.
  • Nothing is recorded until the app calls Blipit.setReplayConsent(true). Text, images, typed input and web content are masked on the device before anything is stored, and the project's Session replay setting decides when it records, as on the web.
  • The session replay guide has a store checklist with ready-to-paste answers for the Google Play Data safety form, an in-app disclosure and a privacy statement for Huawei AppGallery.

Odoo module1.18.10

A richer My report screen in Odoo, and files in team replies

  • My report in Odoo now shows the status, dates and replies at the top, the team's latest reply with its files, what was reported, and a gallery of screenshots, screen recordings, the session replay and every file the team sent. Each one opens full screen, with arrows, swipe, zoom and download.
  • Reply to reporter and internal notes on a bug report take images, videos and PDFs: attach, drop or paste them and watch the upload. Files on a reply reach the reporter's email, tracking page and Odoo; files on internal notes stay with your team.

SDK0.3.19

Browser SDK 0.3.19: stricter masking in replays

  • Readable labels and buttons no longer let values through: anything inside a field value, table cell, kanban card, activity, chat, date picker or popover stays masked even when it is drawn as a button, so dates, payment terms and activity summaries are always asterisks. Also in Odoo.
  • Digits, dates, emails, links and @handles are masked even in readable text (Pay $**.**), title, alt, aria-label and placeholder attributes are masked, and data attributes and email or phone links are removed before anything is sent.

Odoo module1.18.3

Refresh fixed on Odoo 19, and update notices

  • Refresh from Blipit on Workflow health and Pulse works again on Odoo 19.
  • The module now reports its own version, so the dashboard shows Update available when a newer one is on the Odoo Apps store.

Blipit

A live dashboard

  • While the dashboard is open, a new error pops up within seconds, the Issues badge counts new errors and the page you are on updates on its own, with no reload.
  • Every issue has Copy as Markdown: the error, stack trace, breadcrumbs and request in one block to paste into your coding agent.

Odoo module1.18.4

Update emails go to the people in charge

  • The email saying a new Blipit version is out now goes only to the People in charge of each company, not to every Odoo administrator. Administrators still see the update bar inside Odoo.

Blipit

Service desk for bug reports

  • Reporters get an email at every step that matters, each with their reference: received, under review, in progress, waiting on them, fixed (with the version when known), won't fix and reopened. Changes made within a few minutes arrive as one email, and all emails about a report stay in one thread. On every plan.
  • On Solo and up: a page where reporters see all their reports and reply, Waiting on reporter with a reminder and auto-close, saved replies, following reports and merging duplicates.
  • On Team and up: response and resolution targets per priority in your business hours, with Due soon and Overdue alerts, a one-click satisfaction question after a fix, teams, and a service desk report with medians, SLA met and satisfaction. On Scale: targets per team and figures per team member.
  • Reporters can attach a PDF, tell you a fixed report is still broken, and the links in their emails expire some time after a report closes and can be revoked from the report.

SDK0.3.15

Browser SDK 0.3.15: similar reports while typing

  • While someone types the title of a bug report, the reporter shows up to 5 matching reports with their reference and status. This is my problem too adds their notes, screenshots, recording and email to that report instead of opening a new one, and they hear when it is fixed. Also in Odoo, which loads the browser SDK.

Blipit

Reporters show you the problem

  • On the tracking page and the reporter page, reporters can add a screenshot they mark up and blur, record their screen for as long as your plan allows, or attach images, PDFs and videos. Uploads are checked on the server and stay with that one report.
  • New bug reports get references that are unique across your workspace. Where two projects already share a reference, reporters see the project name next to it.

Odoo module1.18.5

My reports shows every status

  • My reports in Odoo now shows Waiting on you, and a status the module does not know yet reads Updated instead of a raw value.

Blipit

Roles and permissions

  • New roles next to Owner and Admin: Developer, Viewer and Billing on Solo and up, and Service desk agent on Team and Scale. Members became Developers and keep exactly what they could do.
  • Invite and Members show each role as a card with what it can and can't do, and a role change saves in place. Preview as this role shows the pages a role would see.
  • On Scale: custom roles with View, Edit and Manage per area, and access to chosen projects only. Projects added later stay hidden from people limited to some projects.
  • Personal data is its own permission. Without it, request details, user emails and IPs, log bodies, replays, reporter contact, screenshots and recordings are removed before the page reaches the browser. Every role change is in the audit log.

Blipit

Times in your time zone

  • Every date and time in the dashboard now shows in your own time zone, with the zone next to times that stand alone and the UTC time when you hover. Charts by day follow your local day.
  • Blipit picks up your browser's time zone on your first visit. Change it any time under Settings, You: search the list or use your browser's time zone.
  • Emails and alerts show times in each recipient's time zone. Emails to reporters use your workspace's business-hours zone, or UTC.

SDK0.3.16

Browser SDK 0.3.16: session replay from the dashboard

  • Each project now has a Session replay setting: Off, On errors and bug reports, or All visits with the share you choose. It works without code changes, also in Odoo, which had no replays until now. A replay option in your own code still wins.
  • Every project starts on On errors and bug reports: the browser keeps the last minute and uploads it only with an error or a bug report, within your plan's monthly replays. Text, inputs and media stay masked in the browser, and the Replays page shows how long your plan keeps them.

Blipit

Web vitals in plain words

  • Each card on Web vitals says in plain words what LCP, INP, CLS, FCP and TTFB measure. Click the name for what it means, why it matters and what usually makes it slow, with a link to the guide. p75 is explained next to the title.
  • The Web vitals guide has a section per metric with Google's good and poor thresholds and how to improve each one, including tips for Odoo.

Odoo module1.18.6

Blipit access rights in Odoo

  • Each Odoo user now has a Blipit access right: Reporter (the Report a bug icon and their own reports), User (also issues, workflows and performance) or Administrator (also settings and people in charge). Odoo administrators are Blipit Administrators.
  • The Report a bug icon no longer shows for every user. On upgrade, administrators, the people in charge and the group chosen in the old setting keep it; give others Reporter in Users, Access rights. Bug reporter 0.3.17 matches “Yours” per Odoo user.

Blipit

Your own Odoo performance alerts

  • Under Alerts, Performance alerts, Your own alerts, New alert lets you build up to 20 alerts per project on top of the four built-in rules.
  • Pick a measure (95th percentile, average or longest time, number of calls, database share of time or queries per call), which actions it watches, your limit, the minutes and the fewest calls that count. Alerts go to the same channels, app owners and on-call. Team and Scale.

Odoo module1.18.2

Faster performance sync, and upgrades on Odoo 20 with Website

  • 1.18.1 reads the performance settings once per sync instead of ten times and uses less memory for each sample.
  • 1.18.2 (Odoo 20 only) fixes the module upgrade on Odoo 20 databases that have the Website app installed.

Blipit

Live data on pull requests

  • On Scale, when a GitHub pull request changes lines of code behind open errors or slow Odoo queries, Blipit posts one comment on it: which errors sit on the changed lines, with their event count and when they were last seen, and in Odoo which slow actions run queries from those lines, with the repeated queries and the slowest run. Each row links to the dashboard, the rest of the changed files sit in a collapsed section, and the comment is updated on every new commit.
  • Errors from every stack are matched exactly through their stack traces, with no AI and no AI credit. Blipit reads only the list of changed files, their changed line numbers and the file tree; no code is sent to AI and query text never leaves Blipit. Turn it on or off per project on the project's GitHub page.

Odoo module1.18.0

Odoo performance: find the slow buttons, screens and scheduled jobs, and the line of code behind them

  • A new Odoo performance page shows the slowest buttons, screens and scheduled jobs in your Odoo, with database time against Python time, repeated queries with the file and line of code that runs them, and a timeline of every scheduled job run. On Solo and up, with a Performance list inside Odoo.
  • On Team and Scale: Slower since tells you when an action got slower after a release or a module upgrade, a Module changes tab shows the before and after of every upgrade, a database health score covers mail, scheduled jobs and queue jobs, and new performance alerts warn you about slow actions, long scheduled jobs and a falling health score. The bug-report widget gets a This is slow button that attaches the page's timings.
  • On Scale: time lost to slowness in hours and money, speed targets per action with an alert, full database health with storage, locks and tables that may need an index, and AI fix for slowness, which explains the cause and can open a pull request.
  • Only counts, durations, queries with their values removed and code locations leave Odoo. Record ids, names, amounts and query parameters never leave Odoo. Upgrade the module to 1.18.0; turn it off under Settings, Blipit, Performance.

SDK

Bug reports from mobile apps: iOS, Android, Flutter and React Native

  • The iOS, Android, Flutter and React Native SDKs now have a Report a bug button, and showReport() to open the reporter from your own menu.
  • The reporter first asks how to show the problem: take a screenshot, record the screen (iOS) or just describe it.
  • The screenshot opens full screen with the tools above and below it, never on top. Pinch, double-tap or use − and + to zoom; pen, box and arrow marks land where you touch. Then add a title and what happened, and send.
  • The .NET and Java SDKs and every mobile SDK now report their version, so the dashboard can tell you when an update is out. Versions: Swift 0.3.0, Android 0.2.0, Flutter 0.2.0, React Native 0.3.0, .NET 0.1.2, Java 0.1.2.

Odoo module1.17.0

Odoo Workflows inside Odoo: a health board, stuck documents and app owners

  • Blipit, Workflows inside Odoo shows every process as a red, amber or green card with its success rate, the people affected, the documents stuck and how long they have waited. Stuck documents opens the orders or invoices themselves. On Solo and up.
  • App owners: pick who owns Accounting, Sales or any app, in Odoo or in Blipit. Owners get that app's workflow alerts and a daily summary by email, with a weekly summary on Mondays. New alerts for documents stuck too long and for a sudden jump in blocked steps, and on-call policies can page on workflow alerts. On Team and Scale.
  • Website checkout steps (cart, checkout, payment) and OCA queue jobs now count as workflows, with a checkout funnel on the Workflows page. Release markers on the trend show when a failure started after a release.
  • On Scale: a success target per workflow with an alert below it, value on hold (opt-in in Odoo settings, sends the total and currency of a document whose step failed) and custom workflows to track and rename your own buttons.

Blipit

Dependencies and Server health: see every database, outside service and server

  • Dependencies: one card per database, cache and outside service your servers call, such as Twilio, Stripe or your PostgreSQL, with calls, response time, failures and availability today. Open a card for charts, the latest failed calls and the slowest ones, each linked to its trace.
  • Server health: CPU, memory, event-loop delay and database connections for each server, live like an activity monitor, with charts for the last hour, day or week.
  • New alerts under Alerts: a dependency failing or slow, high CPU, memory almost full, slow responses and a server that stopped reporting. They go to every alert channel and clear on their own.
  • @blipit/node 0.2.0 and @blipit/nextjs 0.3.0 record all of this with no setup for fetch, http, pg, mysql2 and ioredis, with one line for postgres.js, node-redis and Prisma. SQL values, query strings and bodies are never sent. Other stacks can send OpenTelemetry traces and metrics.

SDK

Node.js and Next.js: serverless requests and one-line setup for Koa, Hono and NestJS

  • @blipit/node 0.3.0: Blipit.wrapHandler records each AWS Lambda request with its database and outside-service calls, reports errors and sends everything before Lambda pauses the function. It only waits when there is something to send.
  • On Vercel the data goes out after the response through waitUntil, so responses are not delayed. In Next.js, withBlipit from @blipit/nextjs 0.4.0 records route handlers and server actions the same way.
  • One line for Koa, Hono and NestJS, next to Express and Fastify. Requests show on the Performance page by route, such as GET /users/:id, instead of one line per URL.

Blipit

Safer sign-in: two-factor on every account, Sign in with Microsoft and a code before you cancel or delete

  • Two-factor sign-in is now required on every account, whichever way you sign in. Blipit walks you through it: scan the QR code with your authenticator app, save your ten backup codes, then enter the 6-digit code. Under Settings you can make new backup codes or change authenticator app.
  • Sign in with Microsoft now sits next to Google and GitHub. On Team and Scale, workspace owners can require Google or Microsoft sign-in for everyone in the workspace.
  • Cancelling a plan, deleting a workspace and deleting your account now ask for a code from your authenticator app or a backup code, on top of the code sent by email.

SDK0.3.13

Browser SDK 0.3.13: faster screenshots on long pages

  • Screenshots on long pages full of images no longer time out. The reporter now only waits for and copies the images and videos in view, and keeps the space of the others so the layout stays the same.
  • Safari and Firefox finish a screenshot in about one to two seconds instead of up to 20.

SDK0.3.12

Browser SDK 0.3.12: a bug reporter made for phones

  • On phones and tablets the reporter first asks how to show the problem: take a screenshot, record a video, attach an image or just describe it.
  • Screenshots open full screen with the zoom above and the tools below, so nothing covers the picture. Pinch to zoom and move with two fingers, double-tap to zoom, or use − and +; marks land exactly where you touch.
  • Record a video walks the visitor through the phone's own screen recorder on iPhone, iPad and Android, hides the reporter while they record and brings it back with one tap to choose the video. The video opens in the editor to trim, mark up and add a voice-over before sending.
  • What the visitor typed is kept in the browser tab for 30 minutes, so nothing is lost if the page reloads while they record. Computers keep the same reporter as before.

Odoo module1.15.0

Odoo Workflows: see which Odoo process is failing, who it stopped and which documents are waiting

  • A new Workflows page in Blipit lists every Odoo business step, such as Confirm quotation, Post invoice, Validate delivery, Register payment and Close POS session, and every scheduled job, with its success rate, the people affected, the documents waiting (each linked back to the record in Odoo), the issues behind the failures and the trend. Buttons from your own modules and their scheduled jobs appear too.
  • Upgrade the module to 1.15.0 and it starts counting, with no setup. Steps Odoo stopped with a message (blocked) are told apart from crashes and timeouts; blocked steps are counted in full and a sample is kept as an event.
  • The order or invoice that failed shows a red banner in Odoo explaining what went wrong, on by default and switched off under Settings, Blipit, Workflows. An optional chatter note is off by default.
  • Two new alerts on the Alerts page: a workflow failing for several people within minutes, and a scheduled job that fails repeatedly or times out. Success rates, the banner and the scheduled job alert come with Solo and up; every plan sees failures, people, documents and causes. Successful steps are sent as counts only, and failed steps add record ids, never amounts, names or messages.

SDK0.3.11

Blipit tells you when an SDK update is out, and browser SDK 0.3.11 keeps its reporter current

  • Browser SDK 0.3.11 loads the reporter, the Report a bug button, the feedback form and session replay from the newest compatible 0.3 build on blipit.io, so npm installs and version-pinned script tags get reporter fixes without a reinstall. Each part checks it supports your installed version and otherwise loads the exact one; sdkChannel: "exact" pins everything to the version you installed.
  • The project page and the projects list in app.blipit.io show a banner when a project sends events from an older SDK: what changed since your version and the update command for your stack, with Copy. Hide it for a version with the cross.
  • Releases marked important or security fix email the workspace owners once, only for projects that sent events from an affected version in the last 14 days. Turn these emails off in Settings or from the link in the email.
  • In development, the browser, Next.js, Node, Python, PHP, Ruby, Go and React Native SDKs print one console line when a newer version is out, with what it fixes and the command to update. It is never shown in production. Python, PHP, Ruby, Go and React Native 0.2.1, @blipit/nextjs 0.2.4 and @blipit/node 0.1.3 also tell Blipit their version so the banner can find them. See Keeping Blipit up to date in the docs.

Odoo module1.16.0

Odoo module 1.16.0: AI fix knows your Odoo

  • The module tells Blipit your Odoo version and edition and the installed modules with their versions, once a day and whenever they change, so AI fix can name the module and version involved. Only technical module names and versions are sent.
  • Errors raised by a button now carry the record's state before the call and the names of the fields being written, never their values, so AI fix can say which step failed and why.

Blipit

AI fix reads your code on GitHub, opens pull requests and learns from past fixes

  • Connect a GitHub repository on the project's GitHub page and AI fix reads the files in the stack trace, and the files they import, at the commit of the release that crashed. Code the AI read shows each file, the lines and the commit, with a link to GitHub. Files that look like secrets are never read and secret-looking values are removed before anything is sent.
  • After an analysis, Open pull request writes the smallest change plus a test, checks that it applies cleanly, and opens a pull request from a new blipit/fix- branch with a link back to the issue. Nothing is pushed to your default branch, and the issue shows when the pull request is merged. It is paid from AI credit at the price shown on the button, and nothing is charged if it fails.
  • AI fix now runs on Claude Haiku 5.5, Sonnet 5.5 and Opus 5.5, tells Claude about similar issues you resolved before and which fix was accepted, and for Odoo issues adds the Odoo version, the model, method and workflow step, and links to the matching lines of Odoo's own code.

SDK0.3.10

Browser SDK 0.3.10: Add voice when a site turns the microphone off

  • When a website's settings turn the microphone off, the reporter now offers Add voice. A small Blipit window opens from your click, asks for the microphone, shows a level meter and Mute, and records your voice while the page records the screen. Pause, resume and stop follow the recording bar.
  • Your voice is saved as its own track next to the video and plays in sync with it in the reporter's preview and on the report in Blipit, with one set of controls and a separate Download voice. Editing the video mixes the voice in.
  • If the browser blocks the window, the reporter says how to allow it; if the window is closed during a recording, the video is kept and the voice is marked as ending early. The video editor's voice-over uses the same window. Phones and tablets show the steps only.

Odoo module1.14.1

Odoo now loads the newest browser SDK, and Odoo module 1.14.1

  • Odoo installs load the newest browser SDK (0.3.9) from their next sync with Blipit, so they get the screenshot fix, the Content Security Policy fixes and the microphone and screen permission guide. Nothing to install: later SDK releases reach Odoo the same way.
  • How to upgrade in the update bar, the Settings banner and the notification now says: download the new version from the Odoo Apps store, or update the blipit_monitor folder in your addons.

SDK0.3.9

Browser SDK 0.3.9: the reporter explains a blocked microphone and how to turn it on

  • Before a screen recording starts, the reporter checks screen sharing and the microphone. When one is blocked it says why in plain words (the website turned it off, you blocked it for this site, your computer blocks the browser, or there is no microphone) and shows the steps for your own browser and system, with Try again, Record without voice and, when screen recording is off, Attach a video instead.
  • During a recording without sound the bar says Voice off — how to turn on, and the video editor's voice-over uses the same check and steps. When the site's Permissions-Policy blocks the microphone, a For the site's developer section shows the one-line header that fixes it.
  • The minimized recording bar no longer jumps back to the middle when you move the mouse to it, so Stop stays under your cursor.

Odoo module1.14.0

Odoo shows administrators a bar on every screen when a Blipit update is out

  • While Blipit is connected, administrators see a bar at the top of every Odoo screen, like Odoo's own database expiration bar: Blipit 1.14.0 is available, you have 1.13.0. How to upgrade shows the steps and the Odoo Apps store link, and the cross hides it for that version.
  • Below the oldest supported version the bar turns red and stays until you upgrade. Errors and bug reports keep flowing in the meantime.
  • Only administrators see it, in every language including right-to-left ones and on phones, and it adds no request to page loads. The Odoo 20 version now also has My reports and the update notices.

Blipit

Screen recordings upload through in.blipit.io

  • Bug report videos now upload to in.blipit.io, like screenshots and events, instead of going straight to the storage provider. A site's Content Security Policy needs only connect-src https://in.blipit.io, and recordings also work behind company proxies that block storage hosts.
  • Nothing to update: every browser SDK version and the Odoo module get this from the server. You can remove https://*.r2.cloudflarestorage.com from your policy.

SDK0.3.8

Browser SDK 0.3.8 and @blipit/nextjs 0.2.3: fixes from a test pass in real apps

  • The Report a bug button, the reporter and the screenshot now work on sites with a strict Content Security Policy, without style-src 'unsafe-inline'. If img-src does not allow data:, the reporter says the screenshot could not be taken instead of showing a blank one.
  • Videos keep their place and size in the screenshot, with the current camera frame, so the page layout and the picked element line up. The same error reported twice, for example by error.tsx in React's development mode, is sent once.
  • @blipit/nextjs works with the Pages Router again: next build no longer stops at Cannot find module next/navigation. blipit.js is back under 10 KB gzipped, because its simple fallback form now loads only when it is needed.

SDK0.3.7

Browser SDK 0.3.7 and @blipit/nextjs 0.2.2: the official Report a bug button

  • Blipit.reportButton() and <BlipitReportButton /> put a ready-made Report a bug button with the Blipit icon anywhere in your pages, in the visitor's language: solid, outline or ghost, two sizes, and light, dark or matched to your page. It opens the reporter, shows a spinner while it loads, and your CSS cannot change it.
  • React apps without Next.js import the component from @blipit/nextjs/react. The Bug report button guide now starts with the official button and has a short section on using the Blipit logo, with the icon to download.

SDK0.3.5

Browser SDK 0.3.5 and @blipit/nextjs 0.2.1: Blipit tells you why it is not running

  • A missing key now logs a clear [blipit] warning in the browser console instead of doing nothing, and <Blipit /> says to set NEXT_PUBLIC_BLIPIT_KEY and restart the dev server. A secret key (blipit_sk_) in browser code is refused with an error.
  • With debug on, the console says whether the Report a bug button was shown, turned off in code or hidden by the project setting, and when the widget settings could not be loaded. updateWidget changes or removes the button while the page runs.
  • blipit.io/sdk/blipit.js serves the latest version again, with the reporter editor next to it. The new Bug report button guide shows every option with screenshots and a live demo, and every install guide now walks through the keys step by step.

Odoo module1.13.0

Odoo tells administrators when a Blipit update is out

  • Settings, Blipit shows administrators the installed and the latest version, a link to the Odoo Apps store and the three upgrade steps. When a new version first appears, every administrator gets one Odoo notification.
  • A version Blipit no longer supports shows administrators a red banner on the Blipit screens. Errors and bug reports keep flowing until you upgrade.
  • Odoo cannot replace a third-party module's files on its own, so the upgrade is still yours: new files, then Upgrade in Apps.

Blipit

People who report a bug now hear back

  • Every bug report gets a reference per project, like BR-12, shown in the widget after sending (browser SDK 0.3.4). A reporter who leaves an email gets a receipt in their own language with a link to follow the report.
  • On a report, Reply to reporter emails your answer, while Internal note stays with your team. Moving a report to In progress, Done or Won't fix offers an email in the reporter's language that you can edit or skip. Receipts, statuses, sender name and Reply-To are set per project under Bug report widget, and every email has a one-click unsubscribe.
  • Odoo module 1.12.0: every Odoo user finds their own reports under Blipit, My reports, with status and replies, and gets an Odoo notification when either changes.

SDK0.3.2

Browser SDK 0.3.2: edited videos are never lost

  • A screen recording edited in the video editor is always sent with the report. If a video cannot be uploaded, the reporter says so: it keeps the report open with Retry, or names the reason, and never shows a plain success.
  • A video longer than the plan allows or larger than 60 MB is named as the reason instead of the storage-full message, and the other attachments still upload.
  • Send waits while a video is being prepared, and when an edited video cannot be prepared the original recording is kept with a message.

Odoo module1.11.3

Connect without a reload, and Disconnect

  • Settings, Blipit: Connect no longer saves and reloads the whole settings page. It shows a spinner while it connects, confirms with a message and turns into a Disconnect button. A wrong key shows the reason and the button stays usable.
  • Disconnect stops errors and bug reports from that database and releases the key on Blipit, so another database can connect to it. The secret key stays in Odoo, so connecting again is one click.
  • Changes to other settings stay in the form while you connect or disconnect, and Save never connects on its own.
  • For integrations: POST /api/v1/sdk/deactivate releases an installation's binding. See the API reference under SDK activation.

Odoo module1.11.2

Report a bug from the Odoo top bar

  • In the Odoo backend, Report a bug is now the coloured Blipit logo in the top bar, just before Discuss, on desktop and on phones, and it stays clear on dark top bars. The website keeps the floating button.
  • JavaScript errors from Odoo users who have no email address are recorded again. Before, Blipit refused them.
  • Browser errors carry the company the person was working in, so company filters and alerts to the people in charge work for them too.
  • The messages shown when refreshing issues fails, and the note on issues that came back after a fix, can be translated with Odoo language packs.

SDK0.3.1

Browser SDK 0.3.1: icon-only button and your own button

  • Bug-report screenshots work again on Odoo 20, where an icon id with dots stopped the capture.
  • The Report a bug button can be a round icon only: pick Button style in the project's widget settings, or set style: "icon" in code. The text stays as the tooltip and the screen-reader label.
  • New guide, Use your own button: hide the floating button with feedbackWidget: false and open the reporter with openReport() or attachReport(element), now also exported by @blipit/nextjs.

Blipit

Issues older than your plan's history are locked

  • Issues last seen before your plan's history window (the days errors are kept) stay in the list, greyed out with a lock and "Older than your plan's N-day history". They can no longer be opened, resolved, ignored or snoozed; clicking one explains why and links owners to Usage.
  • They no longer count as unresolved on the overview and the project page.
  • If the error happens again the issue unlocks on its own, and a plan with a longer history opens older issues again.
  • For integrations: the issues API and MCP add locked and history_days to every issue, return a locked issue without its latest event, and answer 409 to a status change.

Odoo module1.11.5

Older issues locked in the Blipit app

  • Issues older than your Blipit plan's history are greyed out in Blipit, Issues, with an "Older than your plan's N-day history" badge. Clicking one shows how to upgrade instead of opening it, and Resolve, Ignore and Reopen are not available for it.
  • Odoo no longer keeps the stack trace, request or breadcrumbs of a locked issue. A new occurrence unlocks it at the next refresh.
  • Includes everything in 1.11.4.

Odoo module1.11.4

Bug reports up front on the Odoo Apps page

  • The module's page on the Odoo Apps store now presents bug reports next to error monitoring, with screenshots of the Blipit icon in the top bar, the report editor with drawings and the picked Odoo field, screen recording, and the report in Blipit with its Odoo details.
  • The module is now called Blipit Error Monitoring and Bug Reports, and the plans on the page match blipit.io/pricing.

SDK0.3.3

Browser SDK 0.3.3: the selected attachment fills the stage

  • In the bug reporter, the large area beside the form always shows the attachment selected under Attachments: a screen recording plays there in a large player with Edit video, and a screenshot or an attached image opens with the drawing tools.
  • With nothing attached, the stage shows one message with buttons to take a screenshot, attach an image or record, instead of the same message twice.
  • Removing the selected attachment selects the next one, and a new screenshot, image or video is selected as soon as it is added.

SDK0.3.0

Browser SDK 0.3.0: bug reports from your site

  • A Report a bug button on your site, on by default: visitors mark up a screenshot (arrows, shapes, numbered steps, text, blur, crop), pick the broken element and send it in their own language.
  • Each report carries the console, network requests, recent clicks, the device, the React or Vue component of the picked element, the errors of the page and the last minute of replay when replay is on.
  • Passwords, form values and anything marked blipit-mask are hidden before the screenshot is taken. Turn the button off with feedbackWidget: false or from the project settings.

Odoo module1.11.0

Bug reports in Odoo, served by Blipit

  • A Report a bug button in the backend and on the website: people mark up a screenshot, pick the field that is wrong and send it. Each report says which model, record, view, action and field it is about.
  • Settings, Blipit chooses who sees the button: internal users, website visitors, both or nobody, optionally only one group. The signed-in user's name and email are filled in.
  • The module no longer bundles the browser SDK. Blipit serves it, so new capture and report features arrive without upgrading the module.

SDK0.1.0

Blipit packages for every platform

  • PHP: composer require blipit/blipit. Ruby: gem install blipit. Go: go get github.com/blipit-io/blipit-go. Java and Kotlin: com.github.blipit-io:blipit-java via JitPack.
  • React Native: npm install @blipit/react-native. iOS and macOS: the BlipitSwift package from github.com/blipit-io/blipit-swift. Android: com.github.blipit-io:blipit-android via JitPack.
  • .NET: dotnet add package Blipit. Flutter: flutter pub add blipit_flutter, under the blipit.io publisher on pub.dev.
  • Every package takes the public key and project id; no DSN to type. Each wraps the open-source client for its platform, so framework integrations come for free.

SDKPython 0.1.0

pip install blipit

  • The blipit package on PyPI: init with the public key and project id, manual capture, login attempts, and every Django, Flask, FastAPI and Celery integration of the client underneath.

SDKnpm

Blipit packages on npm, and @blipit/nextjs

  • @blipit/browser, @blipit/node and @blipit/cli are published on npm.
  • New @blipit/nextjs: one component in the layout for browser errors, web vitals and replays, and one line in instrumentation.ts for server errors.
  • The docs and the Keys page install with these packages; apps on the previous library keep reporting with a Blipit DSN.

Odoo module1.10.0

Ready for translation

  • Every message the module shows, including errors, the seat count and connection messages, goes through Odoo's translation system, so language packs can translate all of it.
  • Since 1.9.10 the store listing links to this changelog, and Connect uses Save so a refused key shows its error at once and the button stays usable.

Odoo module1.9.9

Connecting is one step and every mistake says why

  • Save refuses anything but a secret key and explains where to get one.
  • With a secret key and the agreement ticked, Save connects on its own and shows a Connected toast.
  • A refused key (wrong, replaced, or already bound to another project) shows the reason at once and the Connect button stays usable.
  • Field labels no longer clash with Google reCAPTCHA's Secret Key, which cleared a build warning on Odoo.sh.

Odoo module1.9.3

Where to sign up, right where you need it

  • Settings shows a link to create a free Blipit account until the database is connected.
  • The empty Issues screen links to sign-up.
  • The store listing names app.blipit.io/signup and says plainly that Odoo Online is not supported.

Odoo module1.9.0

Agreement to the Terms and the licence on Connect

  • Connect requires ticking agreement to the Blipit Terms of Service and the module licence; Blipit records who agreed and to which version.
  • The agreement only counts once Blipit has accepted the key for that database.

Blipit

Terms acceptance, API keys page, seats that mean one thing

  • Everyone accepts the current Terms before using the dashboard; the version, time and address are kept, and a new version asks again.
  • API keys has its own place in the sidebar: every project's public key and a button that creates a secret key.
  • A seat is any person who receives alerts or uses the workspace: members, invites, email alert rules and Odoo people in charge share one count.
  • Owners and admins can remove a project; the New project page shows plan limits up front with a link to plans.
  • SMS and phone calls are hidden until they are set up; on-call steps that asked for them email instead.

Blipit

Logs, tracing, session replay, on-call, releases, synthetic checks

  • Logs: JSON, NDJSON and OpenTelemetry, with live tail and search.
  • Tracing: transactions from the previous library and OpenTelemetry traces, a Performance page, waterfalls and N+1 detection.
  • Session replay with masked text and inputs, a player, and Watch replay on issues.
  • On-call schedules, escalation policies and incidents with acknowledge links.
  • Release health, deploys, suspect commits, code owners and user feedback.
  • Uptime checks for SSL, domains, TCP, DNS and response time, with multi-region majority.
  • Status pages, Jira, Linear and Microsoft Teams, snooze and sampling, two-factor sign-in and an audit log.
  • MCP endpoint for Claude Code and Cursor; web vitals.

SDK0.2.0

Browser SDK 0.2.0

  • Web vitals, session tracking, a feedback dialog and the replay loader; about 7 KB gzipped.

Odoo module1.8.3

Store listing and a seat-count fix

  • New listing with real screenshots and a banner.
  • A failed plan refresh no longer resets the seat count.

Blipit

Pricing v3 and compatibility with the previous library

  • Free 100,000 events; Solo $9, Team $29, Scale $79 a month, or 2 months free yearly. Never billed per event.
  • Apps on the previous library report to Blipit unchanged; uptime monitors and cron heartbeats; AI fix paid from prepaid credit.

Odoo module1.8.1

Only Blipit users can trigger a sync

  • Refresh from Blipit is limited to the Blipit group.

Odoo module1.8.0

Proprietary licence, seats enforced by the server

  • The module is licensed under the Odoo Proprietary License v1.0.
  • People in charge are pushed to Blipit, which checks the seat count and sends the alert emails.

Odoo module1.7.0

Multi-company and login monitoring

  • Every error carries the company it happened in; issues show their companies; people in charge per company within the plan's seats.
  • Login monitoring can be turned on: failed, blocked and successful sign-ins with IP and database, never the password.

Odoo module1.4.2

First store listing

  • Readable SDK build, store banner and a support contact.

Odoo module1.1.0

Blipit as an Odoo app

  • Issues are listed inside Odoo and synced every 10 minutes or on Refresh; resolve, ignore and reopen from Odoo.
  • Regressions are marked when a fixed issue comes back; framework frames are told apart from custom code.

Odoo module1.0.0

First release

  • Unhandled Python exceptions and uncaught JavaScript errors reported to Blipit, bound to one database per key.