SocketIOCocoa icon indicating copy to clipboard operation
SocketIOCocoa copied to clipboard

Bugs when Alamofire and Starscream are already imported as projects

Open longbowww opened this issue 10 years ago • 7 comments

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.

longbowww avatar Dec 05 '14 03:12 longbowww

Hi @longbowww , Try using "request" instead of "Alamofire.request", this project does not wrapped namespace for alamofire. Wish it works if you have the same issue with me :)

raymondos avatar Dec 05 '14 03:12 raymondos

Yap, it is bad and will be fixed when Cocoapods .36 out.

shuoli84 avatar Dec 08 '14 08:12 shuoli84

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. :)

longbowww avatar Dec 10 '14 10:12 longbowww

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

shuoli84 avatar Dec 11 '14 02:12 shuoli84

event is working fine, but unfortunately i cant get my other alamofire rest requests working when i import your vendor folder into my project

longbowww avatar Dec 13 '14 14:12 longbowww

How you import the alamofire?

shuoli84 avatar Dec 14 '14 14:12 shuoli84

i linked the library like they say on their github page - btw i found the solution:

  1. delete your alamofire.swift from vendor files
  2. add "import Alamofire" to EngineTransport.swift
  3. fix EngineTransport.swift, Line 324 from
self.postingRequest = request(.POST, 

to

self.postingRequest = Alamofire.request(.POST, 

longbowww avatar Dec 14 '14 18:12 longbowww