Skip to content

BlueBubbles Server v1.9.7

Latest
Compare
Choose a tag to compare
@zlshames zlshames released this 21 Apr 21:05
· 117 commits to master since this release
c8fd023

What's New?

This update brings some much needed performance improvements to the server, reducing overall CPU utilization and DB query times. In addition, there are a handful of other bug fixes included in this release.

Warning / Note

Apple has flagged my Apple Developer account, which prevents me from signing the BlueBubbles Server with my developer certificate. As a result, you may need to "Allow" the app to run via your System Preference's Security & Privacy page. Alternatively, you can right click the app and select Open to directly open the app.

image

Due to this issue, the BlueBubbles auto-updater no longer works, and you will need to manually perform server updates. Blame Apple. I've tried contacting them, and they've pretty much just ignored my requests.

Changes

  • Vastly improves server performance and reduces CPU utilization by replacing scheduled polling with event-driven polling.
    • Fixes spinning beach ball upon server start
  • Fixes TTL for Firebase messages causing pending notifications to never be delivered
    • This typically occurred when your device was not connected to the internet when a notification should have been delivered
  • Database polling improvements
    • Fixes race conditions during polling
    • Fixes issue causing some events to be ignored when previous events fired successfully
    • Improves handling of updated messages (edited, delivered, read, unsent, etc.)
  • Fixes issue where the server would notify for all new DB entries during an iCloud sync, even if they were not for new messages
    • This may have caused your Firebase messages to be rate-limited temporarily
  • Fixes issue where scheduled messages scheduled more than 24 days out may get triggered immediately

Useful Links

Clients

Enjoy!

P.S. If you are on Cloudflare, expect a disconnect status when the server first starts. To fix it, either disconnect from WiFi or flush your DNS cache on WiFi. If you use the Detect Localhost Address option, this can be mitigated while on your home network.