Releases: bugfender/BugfenderSDK-iOS
Releases · bugfender/BugfenderSDK-iOS
1.6.6
- Added new log levels BFLogWarn, BFLogErr, BFLogFatal, BFLogTrace, BFLogInfo
1.6.5
1.6.5
- The device identifier, the session identifier and sending an issue (issue, crash or user feedback) will return now URLs to the Bugfender's Dashboard. This can be used to create automations and to integrate BugfenderSDK with third party tools
- Fixed race condition that may prevent some crashes to be correctly displayed in the Bugfender's Dashboard
- Added new method allowing developers to manually send crash reports to Bugfender
1.6.4
- Fixed an async task that may block a background thread
- Improved how user defined key-values synchronize with the server
- Fixed race condition that may lead to a heap corruption in low connectivity conditions
1.6.3
Fixed threading issue that may lead to a crash under stress conditions
1.6.2
- Improved the memory footprint of BugfenderSDK. The SDK, in general, will need less memory to perform normal operations
- Improved the behaviour of the SDK heartbeat for apps which are never fully closed
- Fixed crash when a device was trying to send an abnormally big amount of logs to the server
- Logs have been limited to 32000 characters in order to avoid memory issues in devices with low resources available
- Updated docs regarding to the ussage of the tags
- Other minor performance issues
1.6.1
- Fixed crash when using the Bugfender User Feedback in Swift
- Improved return key type in the User Feedback textfields
1.6.0
- Featuring the new Bugfender User Feedback. A fast and easy way to gather feedback from the users
- Fixed swift bridges sending the full path of the files instead the filename
1.5.6
- Addressing issue with gap logs
1.5.5
- Addressing an issue in which access to the iOS keychain in the background may cause a crash
- Fixed SDK sending wrong timestamp in crash
1.5.4
- Fixed when receiving a big number of logs per seconds the SDK may use a lot of RAM and the app may crash. New implementation will ignore new Log operations if it receives a memory warning until the Log queue is reduced.