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
ℹ Please fill out this template when filing an issue.
All lines beginning with an ℹ symbol instruct you with what info we expect. You can delete those lines once you've filled in the info.
Per our *CONTRIBUTING guidelines, we use GitHub for
bugs and feature requests, not general support. Other issues should be opened on Stack Overflow with the tag alamofire.
Please remove this line and everything above it before submitting.
I've created and publish an application on iOS, this application use Alamofire v5.4.3 to communicate with the restful api. We also shipped the application with Firebase Crashlytics, and I received some crash logs which related to Alamofire. I've attached the crash log below. Please check it for me.
iPhone 12 Pro/ iOS 16.0.0
What did you expect to happen?
No crash
What happened instead?
Crash
Alamofire Environment
Alamofire Version: 5.4.3 Dependency Manager: Swift Package Manager Xcode Version: XCode 14.1 Swift Version: Swift 5.7 Platform(s) Running Alamofire: iOS 16.0.0 macOS Version Running Xcode: 12.6.1
Are you using any EventMonitors? If not, you can essentially turn the feature off by passing an empty array when you create your Session instance: Session(..., eventMonitors: []). This may prevent capture by by the CompositeEventMonitor that may be the cause of this issue.
If you are using EventMonitors, an example of your usage may help investigate what's happening.
Are you using any EventMonitors? If not, you can essentially turn the feature off by passing an empty array when you create your Session instance: Session(..., eventMonitors: []). This may prevent capture by by the CompositeEventMonitor that may be the cause of this issue.
@jshier I'm witnessing a similar crash in the CompositeEventMonitor's iteration of monitors. The app is specifying an empty event monitors array (Session(..., eventMonitors: [])) yet an a CompositeEventMonitor is still created with the defaultEventMonitors (AlamofireNotifications). There currently is no way to avoid making the CompositeEventMonitor and AlamofireNotifications in order to avoid the crash. Would it be possible to make the default eventMonitors parameter value be defaultEventMonitors instead of always prepending the defaultEventMonitors to the supplied eventMonitors array? That would allow callers to prevent initializing event monitors they do not intend on using.
What did you do?
I've created and publish an application on iOS, this application use Alamofire v5.4.3 to communicate with the restful api. We also shipped the application with Firebase Crashlytics, and I received some crash logs which related to Alamofire. I've attached the crash log below. Please check it for me.
iPhone 12 Pro/ iOS 16.0.0
What did you expect to happen?
No crash
What happened instead?
Crash
Alamofire Environment
Alamofire Version: 5.4.3
Dependency Manager: Swift Package Manager
Xcode Version: XCode 14.1
Swift Version: Swift 5.7
Platform(s) Running Alamofire: iOS 16.0.0
macOS Version Running Xcode: 12.6.1
Demo Project
The text was updated successfully, but these errors were encountered: