BugSplat

We had a brief hiccup overnight due to a failed automatic database upgrade. Things were resolved by 6 AM EST. Crash reporting & dashboard access may have been spotty for a bit. We’re tightening things up to make sure it doesn’t happen again. Appreciate your patience!

changelog.bugsplat.com

a painting of cherry blossom trees along a river ALT: a painting of cherry blossom trees along a river

Fresh drops from BugSplat (Apr '25):
– Search all symbols 🕵️
– Crash attributes in JS API 🎯
– Native fetch in JS SDK 🌐
– Unreal & Unity SDK updates + fixes 🎮
– Dashboard + UI bug fixes 🛠️
Full changelog 👉 changelog.bugsplat.com

a snowboarder is riding down a snow covered slope with a sticker on his board that says ' salomon ' ALT: a snowboarder is riding down a snow covered slope with a sticker on his board that says ' salomon '

Fresh updates from BugSplat (February '25):

-Edit column filters now available
-Fixed slow dropdown performance
-Unreal SDK gets controller & keyboard support
-Android support improved
-Various stability fixes & tweaks
Full details at --> changelog.bugsplat.com/welcome-to-o...

a man and a woman are skiing down a snow covered path in the woods . ALT: a man and a woman are skiing down a snow covered path in the woods .

Fresh updates from BugSplat (January '25):

-Regression Alerts now live
-Unreal Mac support added
-API & SDK improvements
-Stability fixes & tweaks

Full details at --> changelog.bugsplat.com 🚀

BugSplat Newsletter: January Highlights Get a quick overview of BugSplat's monthly newsletter! This month features Regression Alerts, our Postman API Collection, the Gameye Report on multiplayer game best practices, and the new BugSplat Mon...

January highlights up on our blog - we talk about new features like Regression Alerts and Postman integration. We also give you a chance to solve our monthly puzzle for a chance to win some sweet headphones.

Check it out! blog.bugsplat.com/bugsplat-new...

Beautiful kitty! Ohh and the crash post limit increase is cool too.

New year means improvements to our Changelog! Come and join the fun at @bugsplatchangelog.bsky.social.

Ohh and it's all at changelog.bugsplat.com - duh

Love mechanical keyboards? So do we. 🧑‍💻💥

We’re giving away TWO $100 gift cards to purchase them on our Discord!

Hop in, say hi, and click the 🎉 emoji in #General to enter. Winners announced Dec 29th.

Join here: discord.com/channels/664...

#win #mechanicalkeyboard #crashreporting #softwaredev

Crash Report Upload Limit Increased to 100 MB BugSplat's default crash POST size limit has been increased to 100 MB, giving developers more flexibility to include logs, screenshots, and attachments. Need more space? Contact support@bugsplat.com t...

Quick update: BugSplat's default crash report upload limit is now 100 MB. More room for logs, stack traces, and whatever else you need to fix bugs faster.

Need more space? Reach out: support@bugsplat.com.

Full details: blog.bugsplat.com/crash-report...

In summary:
Uncaught crashes hit everything—reputation, revenue, support costs, and security.

An automated workflow to find & fix bugs protects your app, your team, and your users.

👉 Start using BugSplat for free: app.bugsplat.com/v2/sign-up

#freetools #freesoftware #crashreporting #bugfix

5/ Security Risks 🔒
Crashes often hint at vulnerabilities.

Waiting for users to report bugs = waiting too long.

Monitor crashes early to catch risks before they escalate.

Fix vulnerabilities before they’re exploited.

4/ Increased Support Costs 🔧
Uncaught crashes = more complaints, more tickets, more work.

Support load grows → devs spend less time on new features.

Automate bug tracking early to avoid snowballing tech debt and save dev resources.

3/ Higher Customer Acquisition Costs 📈
Bugs kill word-of-mouth referrals—your most cost-effective marketing tool.

Without organic growth, companies rely on expensive ads to bring users in.

Pro tip: Fix bugs → make marketing & sales easier.

2/ Revenue Loss 💸
Reputation damage hits revenue directly.

If users lose trust, they jump ship. Switching costs are low, and alternatives are everywhere.

Fewer loyal users = less predictable growth. Fixing bugs = keeping the competition at bay.

1/ Reputation Damage 🚨
Apps that don’t capture defects leave themselves vulnerable to two types of damage:

Users abandoning buggy apps (88% stop if they encounter consistent issues).

Negative word-of-mouth online—Reddit, Bluesky, app stores, forums—that lasts.

Fix bugs before they spread.

🧵 How Uncaught Crashes Can Damage Your Reputation, Revenue, + More

We’ve seen firsthand how unmanaged bugs ripple through teams and companies. Let’s break down why capturing and fixing crashes matters—and how it impacts your users, team, and bottom line.

#crashreporting #gamedev #bugs #softwaredev

We're aware some users experienced login issues tonight due to an AWS Cognito incident in the US-EAST-1 region (6:30–8:30 PM MST).

Symbol uploads were also briefly affected, but crash reporting continued normally.

AWS reports recovery, and we’re monitoring closely.

Thanks for your patience!

And crash reporting is the way you document the evidence so you can explain it to the jury!

Anyone really, really proud of a #bug they recently fixed?

#crashreporting #softwaredev #devtools #gamedev

From the ProgrammerHumor community on Reddit: buggyBugs Explore this post and more from the ProgrammerHumor community

Fun discussion on r/ProgrammerHumor: What do you think about the statement "Learn to code and you'll never complain about bugs in software or videogames ever again"

www.reddit.com/r/Programmer...

#computerbugs #videogames #gamedev #programmerhumor

Curious how Custom Attributes work? It's easy! Just use the setAttribute() method in BugSplat.h to upload new attributes during a crash.

Check out the docs for a quick guide: docs.bugsplat.com/education/ho...

What will you track first?

#bugsplat #crashreporting #devtools #gamedev #C++

We recently released a feature that allows you to define custom attributes you can attach to uploaded crashes. These new attributes are fully searchable and viewable in our column view.

This helps you include additional rich context to each crash upload - which helps you find fixes faster.

Building a company or community that creates awesome tools for developers?

We're building a Dev Tools Starter Pack to highlight the best in the industry.

Want to be included? Reach out and let’s showcase your work: go.bsky.app/LTjySum

31/150 (Still room for more!)https://go.bsky.app/LTjySum

10/ Identifying the top 20% of bugs isn’t just about saving time—it’s about providing a smoother, more stable experience for your users.

Ready to optimize your bug-fixing process? Dive into the full post: blog.bugsplat.com/the-80-20-ru...

9/ Step 6: Take it further with custom attributes.

Add more context to your crash reports to better understand the conditions that caused the issue.

More data = smarter fixes.

Learn more: docs.bugsplat.com/education/ho...

8/ Step 5: Integrate crash data into your workflow.

With BugSplat's Jira, GitHub, Favro, Monday(dot)com, and many other integrations, you can seamlessly move from crash detection to defect resolution.

Efficiency = happier teams + happier users.

7/ Step 4: Set up alerts for critical crashes.

BugSplat lets you configure automated notifications via tools like Slack, MS Teams, Discord, and email.

You’ll know immediately when something needs attention—and your users will either not notice anything is wrong or thank you for the quick fix!

6/ Step 3: Analyze crash trends.

BugSplat's Summary page is your home base for identifying trends and outliers in your crash data.

Find the top offenders, prioritize them, and start fixing.

5/ Step 2: Use crash grouping to spot patterns.

BugSplat’s crash grouping organizes defects by type, stack trace similarity, and other factors.

This helps you quickly zero in on the frequent offenders.

4/Step 1: Collect crash data from your production environment.

You need real-world insights to understand how your app behaves when it’s in the hands of users.

BugSplat (www.bugsplat.com) makes this easy—just ensure crashes are being logged properly.