Releases: rollbar/rollbar-apple
3.0.1
What's Changed
- Podspec updates and code changes friendlier to Cocoapods by @matux in #283
- Pod for RollbarCrashReport module and other cocoapods fixes by @matux in #285
- Merging approved feature/cocoapods branch by @matux in #286
- Prepare for 3.0.1 release by @matux in #287
- Fix evil cocoapods by @matux in #288
- Fixed warnings compiling some old ObjC code when using cocoapods by @matux in #289
Full Changelog: 3.0.0...3.0.1
Contributors
Assets 2
3.0.0
Changelog
New features
- The crash collection and reporting mechanism has been redone from scratch, this now allows us to:
- Collect and report all types of crashes together with full stack trace information.
- Provide useful error descriptions on all use cases that trigger crash reporting.
- Produce Swift diagnostics for all types of crashes.
- Format full crash reports with extra diagnostic information.
- Initialization has been simplified:
- Crash collection is now fully automatic.
- There's no need to investigate and select crash reporting libraries in order to make an informed decision, this is all now automatic and works much better than before.
- The Swift Demo has been greatly expanded and enhanced:
- Demo: Expanded Swift Demo with more types of crashes.
- Demo: Prevent optimizer from erasing crashing funcs that result in noops.
- Demo: Allow users to change access token from the Demo UI.
- A new logging option in the configuration allows users to choose whether they want to drop (default) rate limited API requests, or defer sending them until the next window of time.
- Cleaned up extremely noisy internal logging.
Bugs fixed
- Fixed multiple issues while handling rate limited API requests.
- Fixed an important bug where the library would drop non-200 API responses thus treating all failing requests as retry-immediately.
- Fixed logging not being suppressed, and enabled suppression by default.
- Removed faulty Out of Memory detection that was triggering substantial false positives.
Other
- Remove RollbarPLCrashReporter library.
- Never symbolicate main executable frames.
- Don't send mach diagnostics as title, let the server figure it out.
- Add Rollbar branding to the Readme.
- Minimum Swift version is now 5.0 and minimum deployment is 14.0.
- Cleaned up podspecs, added publishing script.
- Remove old, non-working examples and low quality demos.
What's Changed
- Remove RollbarPLCrashReporter library. by @matux in #246
- Simplify reporting by @matux in #247
- Remove faulty Out of Memory detection by @matux in #248
- Cleanup by @matux in #249
- Collect and report all types of crashes together with full stack trace information by @matux in #250
- Provide useful error descriptions on all use cases that trigger crash reporting. by @matux in #251
- If there's no diagnostic, fallback to exception type. by @matux in #253
- Expanded Swift Demo with more types of crashes. by @matux in #254
- Produce Swift diagnostics for all types of crashes. by @matux in #257
- Formats full crash reports with extra diagnostic information by @matux in #258
- Collect crashes with stacktraces by @matux in #259
- Fixed unsuppressed logging, and suppress it by default. by @matux in #260
- Remove non-existing libs from CI. by @matux in #261
- Never symbolicate main executable frames. by @matux in #262
- Fixed cpu subtype not being correctly identified by @matux in #263
- Prevent optimizer from erasing crashing funcs that result in noops by @matux in #264
- Don't send mach diagnostics as title, let the server figure it out. by @matux in #265
- Add Rollbar branding to the Readme by @paulserraino in #245
- Allow users to change access token from the Demo UI. by @matux in #266
- Cleaned up podspecs, added publishing script. by @matux in #242
- Updated all versions to 3.0.0, minimum Swift version to v5 and iOS to 14 by @matux in #267
- Remove old, non-working examples and low quality demos. by @matux in #268
- Removed non-existing demo projects from the workspace. by @matux in #269
- Updated changelog for 3.0.0-beta. by @matux in #270
- Prepare Demo for TestFlight distribution. by @matux in #271
- Demo: Restart Rollbar with new access token without requiring submission by @matux in #272
- Removed unnecessary RollbarSwift library. by @matux in #273
- Fixed failing crash report test after removing mach diagnosis collection by @matux in #274
- Fix rate limiting with queuing behavior by @matux in #276
- Make rate limit behavior configurable for dropping or queuing by @matux in #277
- Updated changelog for 3.0.0 by @matux in #278
New Contributors
- @paulserraino made their first contribution in #245
Full Changelog: 2.4.0...3.0.0
Contributors
Assets 2
3.0.0-beta
What's Changed
- Remove RollbarPLCrashReporter library. by @matux in #246
- Simplify reporting by @matux in #247
- Remove faulty Out of Memory detection by @matux in #248
- Cleanup by @matux in #249
- Collect and report all types of crashes together with full stack trace information by @matux in #250
- Provide useful error descriptions on all use cases that trigger crash reporting. by @matux in #251
- If there's no diagnostic, fallback to exception type. by @matux in #253
- Expanded Swift Demo with more types of crashes. by @matux in #254
- Produce Swift diagnostics for all types of crashes. by @matux in #257
- Formats full crash reports with extra diagnostic information by @matux in #258
- Collect crashes with stacktraces by @matux in #259
- Fixed unsuppressed logging, and suppress it by default. by @matux in #260
- Remove non-existing libs from CI. by @matux in #261
- Never symbolicate main executable frames. by @matux in #262
- Fixed cpu subtype not being correctly identified by @matux in #263
- Prevent optimizer from erasing crashing funcs that result in noops by @matux in #264
- Don't send mach diagnostics as title, let the server figure it out. by @matux in #265
- Add Rollbar branding to the Readme by @paulserraino in #245
- Allow users to change access token from the Demo UI. by @matux in #266
- Cleaned up podspecs, added publishing script. by @matux in #242
- Updated all versions to 3.0.0, minimum Swift version to v5 and iOS to 14 by @matux in #267
- Remove old, non-working examples and low quality demos. by @matux in #268
- Removed non-existing demo projects from the workspace. by @matux in #269
- Updated changelog for 3.0.0-beta. by @matux in #270
New Contributors
- @paulserraino made their first contribution in #245
Full Changelog: 2.4.0...3.0.0-beta
Contributors
Assets 2
2.4.0
What's Changed
- Major refactoring effort. Ready for a new major Beta release. by @akornich in #236
- Two new Demos (iOS Swift/ObjC) and fixes compilation issues of other Demos by @matux in #239
- Crash while serializing data into JSON. by @matux in #238
- Version update to 2.4.0 by @matux in #240
- Release 2.4.0 by @matux in #241
Changelog
- New SDK Demos for iOS Swift and Objective-C.
- Fixed a rare crash during JSON serialization.
- More robust and more flexible SDK reconfigurability.
- Thread safety by design.
- Fully independent configurability of each individual instance of a logger.
- Flexible and standardized rate limiting control (both locally configured and server enforced).
- Structured payload storage based on Sqlite instead of a flat text file.
- Improved local payload logging based on developer options of a config object. Separately for all the incoming vs transmitted vs dropped payloads.
- Improved internal diagnostics of the SDK with reach debug build assertions.
- Ooptimized payload modification implementation.
- Improved performance of the RollbarThread.
- Improved internal SDK recovery from any unforeseen internal SDK exceptions/errors (including during processing of totally custom user-specified data within a payload).
- General codebase code quality and maintainability improvements.
- A higher level of code reuse.
- And more...
New Contributors
Full Changelog: 2.3.4...2.4.0
Contributors
Assets 2
Hot-fix
Minor fixes
Minor fix
Fix broken Cocoapods build
Fix broken Cocoapods build
- fix: resolve #183 - Fix broken Cocoapods build
Special Release Note
Starting v 2.3.0 release, we added a new experimental feature that detects Out-of-Memory (OOM) application crashes.
Due to the non-deterministic nature of the algorithm used for this, we expect a reasonable number of false-positive detection results. The algorithm is based on the exclusion of other reasons that may have forced an application to terminate until an OOM cause is left as the only very last suspect. Unfortunately, some system APIs used to exclude other causes of application termination are not completely reliable and could result in the false positive outcomes mentioned above.
We expect the actual frequency of these false positives to vary widely based on the concrete runtime environment including device, device model, device configuration, specific *OS, specific *OS version, and app usage profile.
We have the OOM detection ON by default; however, if you would prefer to turn it OFF you can set loggingOptions.enableOomDetection flag to NO when setting up RollbarConfig instance.
In the medium term, we have other improvements on the roadmap that would allow us to reduce (if not completely eliminate) false positives within the next few development iterations.
Let us know what you think about this new feature and how we can improve the SDK.
Thank you for using Rollbar!
New experimental feature and some fixes
New experimental feature and some fixes
- feat: Detection of possible Out-of-Memory issues
- fix: resolve #166 - v2.2.4 spams to log with NSLog on iOS
- fix: resolve #176 - Rollbar crashes when device runs out of memory
- fix: resolve #180 - SonarCloud: address current reliability issues
Special Release Note
In this upcoming v 2.3.0 release, we are adding a new experimental feature that detects Out-of-Memory (OOM) application crashes.
Due to the non-deterministic nature of the algorithm used for this, we expect a reasonable number of false-positive detection results. The algorithm is based on the exclusion of other reasons that may have forced an application to terminate until an OOM cause is left as the only very last suspect. Unfortunately, some system APIs used to exclude other causes of application termination are not completely reliable and could result in the false positive outcomes mentioned above.
We expect the actual frequency of these false positives to vary widely based on the concrete runtime environment including device, device model, device configuration, specific *OS, specific *OS version, and app usage profile.
We have the OOM detection ON by default; however, if you would prefer to turn it OFF you can set loggingOptions.enableOomDetection flag to NO when setting up RollbarConfig instance.
In the medium term, we have other improvements on the roadmap that would allow us to reduce (if not completely eliminate) false positives within the next few development iterations.
Let us know what you think about this new feature and how we can improve the SDK.
Thank you for using Rollbar!