Open vikihleblya opened 2 years ago
Describe the bug AppCenter report this crash Flurry_iOS_SDK -[FlurrySignalConnectionTypeDataProvider onqueue_getCellularSignalConnectionType]
Stacktrace:
libobjc.A.dylib objc_retain CoreFoundation -[NSDictionary allValues] MRMail -[FlurrySignalConnectionTypeDataProvider onqueue_getCellularSignalConnectionType] MRMail -[FlurrySignalConnectionTypeDataProvider onqueue_connectionTypeChanged] MRMail -[FlurryActor wrapAsyncBlock:] libdispatch.dylib _dispatch_call_block_and_release libdispatch.dylib _dispatch_client_callout libdispatch.dylib _dispatch_lane_serial_drain libdispatch.dylib _dispatch_lane_invoke libdispatch.dylib _dispatch_workloop_worker_thread libsystem_pthread.dylib _pthread_wqthread libsystem_pthread.dylib start_wqthread
Please choose the closest item by replacing [ ] with [x].
[ ]
[x]
Platform Please choose the platform(s) that you are having the issue by replacing [ ] with [x].
Environment Please tell us the versions of Flurry SDK, XCode, and iOS you are using.
To Reproduce Steps to reproduce the behavior: Not systematically reproducible
Screenshots There's no helpful screenshots ;(
Additional context Are you using Flurry Push/Messaging? No (iOS) Are you using CocoaPods or manual binary integration? Carthage
Add any other context about the problem here. There was the same issue, but it was fixed for 10.x.x version of SDK
Describe the bug AppCenter report this crash Flurry_iOS_SDK -[FlurrySignalConnectionTypeDataProvider onqueue_getCellularSignalConnectionType]
Stacktrace:
Please choose the closest item by replacing
[ ]
with[x]
.Platform Please choose the platform(s) that you are having the issue by replacing
[ ]
with[x]
.Environment Please tell us the versions of Flurry SDK, XCode, and iOS you are using.
To Reproduce Steps to reproduce the behavior: Not systematically reproducible
Screenshots There's no helpful screenshots ;(
Additional context Are you using Flurry Push/Messaging? No (iOS) Are you using CocoaPods or manual binary integration? Carthage
Add any other context about the problem here. There was the same issue, but it was fixed for 10.x.x version of SDK