-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bugs when Alamofire and Starscream are already imported as projects #7
Comments
Hi @longbowww , |
Yap, it is bad and will be fixed when Cocoapods .36 out. |
I am trying to use it as standalone in a Test project and what I cant figure out is, how do you emit events from the Client Side? Is this function implemented? Connecting and receiving the Handshake works fine. :) |
Not sure whether this is what you asking. After you get a socket, then you can emit message by socket.event("message", data: [1,2,3]) |
event is working fine, but unfortunately i cant get my other alamofire rest requests working when i import your vendor folder into my project |
How you import the alamofire? |
i linked the library like they say on their github page - btw i found the solution:
self.postingRequest = request(.POST, to self.postingRequest = Alamofire.request(.POST, |
Hi,
I have kind of the same issue like the other guy that posted about Alamofire.
I already use it for a lot of REST calls and it wont find the methods anymore when I import your vendor folder. It somehow only checks for your alamofire.swift and doesnt accept calls for the natively imported project file.
The text was updated successfully, but these errors were encountered: