1. 15 10月, 2021 6 次提交
  2. 14 10月, 2021 14 次提交
  3. 13 10月, 2021 7 次提交
  4. 12 10月, 2021 2 次提交
    • P
      test: Fix SentryStacktraceBuilderTests (#1372) · f66fd0f1
      Philipp Hofmann 提交于
      testAsyncStacktraces should be testing if stack traces of different threads
      are stitched together, which it didn't do, because we were only building
      the stack trace on the main thread. This is fixed now by building the
      stack trace across different threads. Furthermore, the tests now use
      their own queue to avoid side effects when testing.
      f66fd0f1
    • P
      test: Remove SentrySwiftTests (#1373) · eb00be75
      Philipp Hofmann 提交于
      SentrySwiftTests don't have a clear testing purpose as it combines
      the test of multiple classes that we cover in more specific test classes.
      eb00be75
  5. 08 10月, 2021 1 次提交
  6. 07 10月, 2021 2 次提交
    • G
      release: 7.4.3 · fea75d38
      getsentry-bot 提交于
      fea75d38
    • P
      fix: Crash for Custom ViewController init on iOS 15 (#1361) · 75e72817
      Philipp Hofmann 提交于
      Swizzle all custom ViewControllers. First, fetch all subclasses of ViewController and then swizzle them. As there is no straightforward way to get all sub-classes in Objective-C, the code first retrieves all classes in the runtime, iterates over all classes, and checks for every class if UIViewController is a parent. Cause loading all classes can take a few milliseconds, do this on a background thread, which should be fine because the SDK swizzles the root view controller and its children.
      Previously, the code intercepted the ViewController initializers with swizzling to swizzle the lifecycle methods. This approach led to ViewControllers crashing when using a convenience initializer, see GH-1355. The error occurred because our swizzling logic adds the method to swizzle if the class doesn't implement it. It seems like adding an extra initializer causes problems with the rules for initialization in Swift, see https://docs.swift.org/swift-book/LanguageGuide/Initialization.html#ID216.
      
      Fixes GH-1355
      75e72817
  7. 06 10月, 2021 2 次提交
  8. 04 10月, 2021 4 次提交
  9. 01 10月, 2021 2 次提交
    • P
      test: Use a set for array comparison (#1356) · cdcfdcb6
      Philipp Hofmann 提交于
      Use a set for array comparison in UIViewControllerSentryTests as we
      don't care about the order of the elements of the array but just if the
      array contains the same elements. Comparing with XCTAssertEqual
      also checks the order and lets the test fail if the order is different.
      cdcfdcb6
    • P
      ref: Specify dict and set types for SentrySwizzle (#1357) · b447d658
      Philipp Hofmann 提交于
      The dictionaries and sets in SentrySwizzle didn't have the types
      specified, which makes the code harder to read. This is fixed now
      by adding the explicit types.
      b447d658