Maybe conflict with OpenUDID about swifthttp HOT 7 CLOSED

ok i solved this problem.

1.comment line 23

//var stringEncoding = NSUTF8StringEncoding

2.replace all self.stringEncoding with NSUTF8StringEncoding

from swifthttp.

Ok good information to know. I think there is a deeper issue with the conflict between the 2 libraries though, as stringEncoding is a property scope in a class, so I would not think there would be any conflicts. I would rather not remove the stringEncoding ivar as it always the flexibility of different encoding types. Do you know if OpenUUID has a stringEncoding variable as well?

from swifthttp.

i think it's not a conflict only between the two libraries.
yesterday i tried to use another BaaS named AVOS Cloud (written by Objc) , also reported this.
i dont know more about OpenUDID, and i don't know the reason for this issue.
but actually replacing all self.stringEncoding with NSUTF8StringEncoding can solve it.

from swifthttp.

Ok, it has to be something with the way it is being exported into the namespace between the swift classes and the objc classes. I am willing to wager those other services/libs have some kind of ivar of stringEncoding as well. I think it worth getting a better answer though, so I will keep this issue open until more research is done into why the conflict is happening.

from swifthttp.

I got a "Ambiguous use of NSUFT8StringEncoding" error at same place with some Objective-C libraries.
So, I changed "stringEncoding" type as UInt, then everything looks fine for me.

var stringEncoding : UInt = NSUTF8StringEncoding

from swifthttp.

@bradex, interesting and thanks for the info. I curious on why that would fix the conflict. I will try and see if I can dig in deeper on what is causing the conflict in the first place, but thank you much for the solution. I will implement that change ASAP.

from swifthttp.

I just checked in @bradex fix. Thanks again!

from swifthttp.