Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfender SDK Crash in v1.10.2 with NSPropertyListSerialization #69

Closed
macfanatic opened this issue Jun 25, 2021 · 11 comments
Closed

Bugfender SDK Crash in v1.10.2 with NSPropertyListSerialization #69

macfanatic opened this issue Jun 25, 2021 · 11 comments

Comments

@macfanatic
Copy link

Bugfender SDK: 1.10.2
Xcode 12.5
Bitcode enabled: yes
Cocoapods: 1.10.1

I just upgraded from 1.9.2 to 1.10.2 after upgrading to Xcode 12.5 and we have noticed a new crash, apparently in Bugfender itself (see below) in crashlytics.

Screen Shot 2021-06-25 at 4 34 43 PM

Crashed: com.apple.root.background-qos
0  CoreFoundation                 0x182e23c14 CFGetTypeID + 92
1  CoreFoundation                 0x182e1510c _CFAppendXML0 + 68
2  CoreFoundation                 0x182e15c60 _CFAppendXML0 + 2968
3  CoreFoundation                 0x182e15c60 _CFAppendXML0 + 2968
4  CoreFoundation                 0x182e1202c _CFPropertyListCreateXMLData + 188
5  CoreFoundation                 0x182e13f2c CFPropertyListCreateData + 220
6  Foundation                     0x1840fbe14 +[NSPropertyListSerialization dataWithPropertyList:format:options:error:] + 52
7  BugfenderSDK                   0x10100e44c _hidden#1830_ + 150 (__hidden#1862_:150)
8  libdispatch.dylib              0x182a9924c _dispatch_call_block_and_release + 32
9  libdispatch.dylib              0x182a9adb0 _dispatch_client_callout + 20
10 libdispatch.dylib              0x182aaba68 _dispatch_root_queue_drain + 656
11 libdispatch.dylib              0x182aac120 _dispatch_worker_thread2 + 116
12 libsystem_pthread.dylib        0x1cdc957d8 _pthread_wqthread + 216
13 libsystem_pthread.dylib        0x1cdc9c76c start_wqthread + 8
@jgimenez
Copy link
Member

Hi there, it would be great to know what's the reason displayed for crash. This usually appears above the screenshot you took. Also, does it happen always or only on some specific devices? Thanks.

@macfanatic
Copy link
Author

We only support iPad devices, and looks like everyone is using iOS 14.

Screen Shot 2021-06-29 at 8 23 20 AM

@jgimenez
Copy link
Member

Thanks for the device information. What about the reason for the crash?

@macfanatic
Copy link
Author

I don't see anything else on this page other than a sidebar on the left to switch between google products. Is there something specifically you want to see and could share steps to get access to?

We log to Bugfender and Crashlytics simultaneously, and I can see that the crash doesn't appear related to any exact action just by reviewing the logs in Crashlytics (ie, different parts of the app, different time periods of usage in the app, etc).

I'm assuming this is crashing when Bugfender attempts to intermittently transmit information on a background thread, as that makes the most sense for the timing.

@jgimenez
Copy link
Member

jgimenez commented Jul 1, 2021

Thanks @macfanatic , this information should be enough to locate the crash. We're already working on it.

@jgimenez
Copy link
Member

jgimenez commented Jul 8, 2021

As discussed in private, this is likely to be a memory corruption issue, not necessarily caused by Bugfender. I'm closing this for now, please feel free to reopen if necessary.

@jgimenez jgimenez closed this as completed Jul 8, 2021
@miraclebg
Copy link

I have exactly the same issue with our app - several crashes since we've added Bugfende
Screenshot 2021-10-27 at 17 30 46
r.

@miraclebg
Copy link

Bugfender: BugfenderSDK (1.10.3)
iOS 15.0.2
iPhone XS Max

@macfanatic
Copy link
Author

Yes, we rolled back to the previous version without any code changes and our crash rate went back to zero. We haven't updated the SDK since to try again.

@miraclebg
Copy link

@macfanatic Which version did you roll back to? 1.10.2 or 1.10.1 ? Thanks! So i can try it too.

@macfanatic
Copy link
Author

We rolled back to v1.9.2, which was the version we had been using in production as well before upgrading to 1.10.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants