Wordpress-ios: EXC_BREAKPOINT: 0@0:8@"CPLLibraryManager"16@"CPLResourceTransferTask"24@"NSError"32 > release

[sentry-io[bot]]

Sentry Issue: WORDPRESS-IOS-1KNV

EXC_BREAKPOINT: 0@0:8@"CPLLibraryManager"16@"CPLResourceTransferTask"24@"NSError"32 > release
  File "NotificationsViewController.swift", line 912, in NotificationsViewController.selectRow
  File "NotificationsViewController.swift", line 910, in NotificationsViewController.selectRow
  File "NotificationsViewController.swift", line 664, in NotificationsViewController.showDetails
  File "NotificationsViewController.swift", line 640, in NotificationsViewController.showDetailsForNotificationWithID
  File "<compiler-generated>", in NotificationsViewController.showDetailsForNotificationWithID
...
(48 additional frame(s) were not displayed)

[designsimply]

39-day impact: ~8 per day
Users affected in the last 39 days: 206
First seen in: 13.2.0.6
Limited to: iOS 13.0 and above

^{https://sentry.io/share/issue/cd08e382d552430f9bd7d215b66516d3/}

[designsimply]

@JavonDavis this is a new crash which (I think) started in 13.2.0.6, is there an easy way to look up the notifications-related PRs for 13.2.0.6?

@aerych since you've just helped fix a notification setup glitch in #12732, does anything in this crash report stand out as related? @frosty same question since you've recently worked on Notifications for Dark Mode (and this crash also seems to be limited to iOS 13).

[JavonDavis]

@designsimply we can filter by milestone... https://github.com/wordpress-mobile/WordPress-iOS/pulls?utf8=%E2%9C%93&q=is%3Apr+milestone%3A%2213.2+%E2%9D%84%EF%B8%8F%22+is%3Aclosed+notification this should give a good idea for 13.2 and https://github.com/wordpress-mobile/WordPress-iOS/pulls?utf8=%E2%9C%93&q=is%3Apr+milestone%3A%2213.2.xx+%E2%9D%84%EF%B8%8F%22+is%3Aclosed+notification+ for 13.2.xx

[aerych]

Hmm. Fun puzzle.

CPLLibraryManager"16@"CPLResourceTransferT is part of CloudPhotoLibrary.framework, and is not called directly from NotificationsViewController.selectRow as far as I can see. Interesting that its release method is being called, which suggests that its about to be deallocated. It's an odd thing to see in the stack trace here.

As far as the crash type, from the docs, EXC_BREAKPOINT

Similar to an Abnormal Exit, this exception is intended to give an attached debugger the chance to interrupt the process at a specific point in its execution. You can trigger this exception from your own code using the __builtin_trap() function. If no debugger is attached, the process is terminated and a crash report is generated.

Lower-level libraries (e.g. libdispatch) will trap the process upon encountering a fatal error. Additional information about the error can be found in the Additional Diagnostic Information section of the crash report, or in the device's console.

Swift code will terminate with this exception type if an unexpected condition is encountered at runtime such as:
    a non-optional type with a nil value
    a failed forced type conversion

Not super helpful, but maybe hints that something in NotificationsViewController.selectRow at line 912 was unexpectedly nil, or was of the wrong type. Its not immediately clear how either could be, and in either case we'd expect a more relevant error message. 🤔

(and this crash also seems to be limited to iOS 13)

Not ruling out a new OS glitch.

@jleandroperez, do you recall if Notifications does anything with CloudPhotoLibrary.framework? If its there anywhere I'm missing it.

[jleandroperez]

@aerych CloudPhotoLibrary definitely has absolutely nothing to do with Notifications.

L912 involves the TableViewHandler, and a simple comparison... maybe we're having symbolication issues?

[aerych]

maybe we're having symbolication issues

Hmm. Maybe. Good thought.

[aerych]

I think we might be able to close this one? Looks like the related issue was marked resolved in 13.9 by @diegoreymendez. @designsimply does that look right to you?

[designsimply]

A search in Sentry for CPLLibraryManager returns zero results at the moment, and I believe we should be able to close because of that. @diegoreymendez do you recall working on this crash and closing it?

[diegoreymendez]

It's so hard to work with Sentry because links seem to break after a while. :(

But I think @aerych is right, and this is most likely related to my work here given the reported file and line numbers.

I'm closing this issue.