You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 15, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 15, 2024. It is now read-only.
Regressed crash on "com.yahoo.flurry.watchconnectivity" from issue (#186) #256
Describe the bug
A clear and concise description of what the bug is.
This Bug is About
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.1.4
XCode: 14.3.1
iOS: 15.7.6
To Reproduce
We're getting this crash in production, but we are not running any watchOS analytics for Flurry and not including FlurryWatchSDK. But the main iOS SDK for Flurry is probably tryin to activate or connect with companion watch app Flurry sdk.
Is there a way to disable this watchOS-specific activity from running since it's causing crashes anyways?
changed the title [-]Regressed crash on com.yahoo.flurry.watchconnectivity from issue #186[/-][+]Regressed crash on com.yahoo.flurry.watchconnectivity from issue (#186)[/+]on Jun 23, 2023
changed the title [-]Regressed crash on com.yahoo.flurry.watchconnectivity from issue (#186)[/-][+]Regressed crash on "com.yahoo.flurry.watchconnectivity" from issue (#186)[/+]on Jun 23, 2023
Activity
[-]Regressed crash on com.yahoo.flurry.watchconnectivity from issue #186[/-][+]Regressed crash on com.yahoo.flurry.watchconnectivity from issue (#186)[/+][-]Regressed crash on com.yahoo.flurry.watchconnectivity from issue (#186)[/-][+]Regressed crash on "com.yahoo.flurry.watchconnectivity" from issue (#186)[/+]flurrydev commentedon Jun 26, 2023
Thank you for submitting the bug report. I will investigate and see if a fix can be added in the next release.