Rename from SentrySwift to Sentry

• We decided to rename SentrySwift to just Sentry

  Version 2.0.0 has the same features as 1.4.5.
  The name of the Framework has been changed from:
  import SentrySwift
  to
  import Sentry
  Also in the Podfile you have to change to pod Sentry instead of pod SentrySwift.
  Everything else stayed the same.

1.4.5

• Now sending registers with stacktrace for better symbolication results
• Added verbose logging option which outputs raw events and crash reports
• Add relevant_address to stacktrace
• Extended mechanism
• Add build to release e.g.: 1.0 (1337)
• Added objcBeforeSendEventBlock as equivalent to swifts beforeSendEventBlock

1.4.4

• Removed SentryClient.shared?.enableThreadNames because KSCrash changed the mechanism on how threadnames are fetched. They will show up in sentry if available.
• Now sending build number with every event.

1.4.3

• Fixed an issue where properties of an event will be overwritten before sending
• Added SentryClient.shared?.enableThreadNames variable which can be set to true in order to retrieve the thread names when a crash happens. Enable this on you own risk this could deadlock you app therefore its not yet officially documented.

1.4.2

• Fixed Xcode 7 support

1.4.1

• enable searchThreadNames to display thread names in sentry

1.4.0

• Update KSCrash to 1.13.x

Warning

• Added namespace for Objc
  e.g.: User -> SentryUser but Xcode should suggest the new class names ... Swift code does not change

1.3.4

• Store events now in Library/Caches instead of Documents folder

1.3.3

• Add RequestManager for improved handling on many requests

1.3.2

• Reuse URLSession when sending events
• Optimize BreadcrumbStore