-
Notifications
You must be signed in to change notification settings - Fork 140
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
EXC_BAD_ACCESS #158
Comments
There must be more to the story that is not included here. I don't think the information provided allows to tell what's going on. The client is not allocating memory by itself or dealing with pointers. Here are some details on how to debug
I am not sure if I can do more - the line you pointed to is being used in many tests and I have never seen |
The client is starting through Objective C using the following code
and the client has the following function:
|
There is no pending action item for this scenario so I am closing this issue. |
I have bridged my app with the library but it gives me the following error constantly
Thread 1: EXC_BAD_ACCESS (code=1, address=0xfffffff9fffbd2ce)
at this line
on this code
self.chatHubConnection = HubConnectionBuilder(url: URL(string: self.url)!)
.withLogging(minLogLevel: .debug)
.withAutoReconnect()
.withHttpConnectionOptions(configureHttpOptions: { (httpConnectionOptions) in
if let header = self.headers {
for (key, value) in header {
httpConnectionOptions.headers[key] = value
}
}
})
.withHubConnectionDelegate(delegate: self.chatHubConnectionDelegate!)
.build()
The text was updated successfully, but these errors were encountered: