1.12.1

• This release fixes problems with Cocoapods and static library in the previous release.

1.12.0

• Feature: Add enableNSLogLogging & enableNSLogLoggingWithInterceptor method that allows to automatically capture logs written via NSLog or OSLog.
• Internal: Changes on library initialization.

1.11.0

• Feature: Add enableUIEventLoggingWithIgnoredViewTags method that allows to avoid generating logs for some views
• Changed setMaximumLocalStorageSize to not throw an Exception if the value provided is out of range.

1.10.6

• Fix: Possible crash due to corrupted crash log
• Feature: iOS device name is not gathered anymore, it has been replaced by the device model.

1.10.5

• Fix: upload symbols script was not working properly

1.10.4

• Add upload symbols script to Bugfender Pod

1.10.3

• Bugfix: user feedback dialog navigation bar sometimes not styling properly
• Bugfix: crashes sometimes reported in the wrong session when the application crashes multiple times in a row

1.10.2

• Bugfix: fixed potential crash when setting custom device data

1.10.1

• Bugfix: fixed potential crash or missing logs when app is in background mode in combination with protected data classes
• More efficient API calls

1.10.0

• Bugfender was compiled with Xcode 12 and is SPM compatible now
• Additionally dynamic framework and static libraries without simulator arm slice are provided for retrocompatiblity but they should be avoided

1.9.2

• Feature: added a new overrideDeviceName(String) that allows to customize the name of the device.

1.9.1

• Fix: returning URLs from device/issue/session missing path segment

1.9.0

• Support for CocoaPods 1.9.0 and xcframework

1.8.0

• Added xcframework to support Project Catalyst
• Bugfender is now a dynamic library and swift files are included inside. No need to manually add the swift bridge anymore
• Bugfender will return a specific -1004 error when trying to send logs to an app that was deleted in the server

1.7.0

• Fixed an issue in which retrieving the session identifier right after activateLogger might result in a null identifier under certain conditions and this could provocate a crash in swift projects
• Changed pulic api so URL dependant identifiers are nullable properties now

1.6.6

• Added new log levels

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

• Fixed an issue in which gap logs were reporting wrong begin/end dates

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.

1.5.3

• Fixed issue with some crashes was not sent.

1.5.2

• Implement refresh device status
• Fixed issue with the device key-values

1.5.1

• Improved efficiency of background cleanup process

1.5.0

• Added crash reporting
• Added information when deleting logs unsent to the server
• Added exponential back off if the server is not reachable

1.4.10

• Added method for setting API endpoint

1.4.9

• Fixed crash when sendIssues is called with nil parameters.
• Adding some other parameter validations.

1.4.8

• Fixed minor issues.

1.4.7

• Fixed minor issues.

1.4.6

• Added method to get the session identifier.
• Now send issue method returns the issue identifier.

1.4.5

• Fixed issue with the latest release.

1.4.4

• Improvements with the CPU consumption.

1.4.3

• Stability update: fixed crash in very rare circumstances.
• Improvements when the sdk is deleting the old logs because the max storage size is reached.

1.4.2

• Fixing CocoaPods when using static libraries in Objective-C
• Now compatible with Swift 2.3, 3.0 and 3.1
• Fixing appledoc, fixToConsole default setting wrongly documented
• Fixing appledoc, some argument names were wrong
• Printing an empty line on BFLog(nil);

1.4.0

• Declared the framework as a Clang module, so that the framework can be used in Swift without bridging headers
• Removed redundant and outdated method calls to make the SDK docs/API cleaner
• Published helper file for Swift projects

0.3.27

• Stability update: fixed crash in very rare circumstances.

0.3.26

• Improved networking code, smaller and more efficient
• Fixed conflict with AFNetworking library

0.3.25

• enableNSLogLogging is now marked as deprecated, not working since iOS 10
• Dropping support for iOS 7
• Improvements on the networking code

0.3.24

• Better formatting of the automated user interaction logging

0.3.23

• Fixing missing some NSLogs at the beginning and end of the session, especially on iOS 10
• Fixing documentation warnings raised by Xcode 8
• Fixing duplicated logs from NSLog when DEBUG macro is defined when using BFLog

0.3.22

• Fixing bug that sends empty sessions to the server
• Fixing a bug that reports wrong app version information when the build number contains the dot character

0.3.21

• Fixing wake lock to avoid applications dying faster in the background

0.3.20

• Bug fix: date formatting in devices in Arabic
• Improves: format for UI events

0.3.18

• fixing nil dereference exceptions (rarely seen)

0.3.17

• Fixes synchronization of device details set with setDevice*
• Allows the change of the API endpoint via environment variable for Bugfender preproduction tests

0.3.16

• Fixes #11, crash when using Bugfender with CocoaLumberjack and empty log message

0.3.15

• Fixes timestamp estimation and some UIEvents without timestamp.
• Better description for topmost view controller and UIEvents

0.3.14

• Recompiled with Xcode 7, supports Bitcode

0.3.10

• Fixed crash on iOS7 when NSLog logging is enabled
• Added documentation about issues

0.3.9

• Added issues
• Option to send logs from the app

0.3.8

• Added device detail key-value storage
• Fixed a crash when device disk was full

0.3.7

• Efficiency and stability improvements

0.3.6

• Automated logging of NSLog
• Automated UIEvent logging
• Efficiency and stability improvements