Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

App Crash with 12.0.1 -[FlurrySignalConnectionTypeDataProvider onqueue_getCellularSignalConnectionType] #248

Open
2 of 11 tasks
vikihleblya opened this issue Aug 5, 2022 · 0 comments
Assignees
Labels

Comments

@vikihleblya
Copy link

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].

  • Integration
  • Analytics
  • Ads
  • Messaging/Push
  • IAP
  • Remote Configuration
  • Flurry Website/Dashboard
  • Other

Platform
Please choose the platform(s) that you are having the issue by replacing [ ] with [x].

  • iOS
  • tvOS
  • WatchOS

Environment
Please tell us the versions of Flurry SDK, XCode, and iOS you are using.

  • Flurry SDK: 12.0.1
  • XCode: 13.3.1
  • iOS: 15.6, 15.5, 15.4.1 (most affected OS according to AppCenter)

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

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

No branches or pull requests

3 participants