Skip to content
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

[MQTTWebsocketTransport setUrl:]: unrecognized selector sent to instance #492

Closed
stellz opened this issue Aug 17, 2018 · 5 comments
Closed

Comments

@stellz
Copy link

stellz commented Aug 17, 2018

Few minutes ago I updated my pods using "pod update" and noticed that MQTTClient updated.

Installing MQTTClient 0.15.0 (was 0.14.0 and source changed to https://github.com/CocoaPods/Specs.git from https://github.com/cocoapods/specs.git)

After running my project I immediately received a crash:

[MQTTWebsocketTransport setUrl:]: unrecognized selector sent to instance
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[MQTTWebsocketTransport setUrl:]: unrecognized selector sent to instance

@jcavar
Copy link
Contributor

jcavar commented Aug 17, 2018

Did you have version from master before?
Could you paste diff produced by pod update?

@sudhamoorthi
Copy link

Hi, i am also facing the same issue. How do you resolve this issue?

@stellz
Copy link
Author

stellz commented Aug 20, 2018

@jcavar Unfortunately I can't paste the diffs, but yes, I think the previous version was from the master branch. I joined the project that I'm working on recently and don't have much info about the initial start.

@sudhamoorthi I just changed the version to the previous one editing the Podfile

pod 'MQTTClient', '0.14.0'

@jcavar
Copy link
Contributor

jcavar commented Aug 20, 2018

That is weird. Can you try changing

https://github.com/novastone-media/MQTT-Client-Framework/blob/master/MQTTClient/MQTTClient/MQTTWebsocketTransport/MQTTWebsocketTransport.m#L22

from @dynamic to @sythesize

locally in your pod?

@jcavar
Copy link
Contributor

jcavar commented Aug 21, 2018

This is now resolved in 0.15.1 release, please update your pods. Thanks for reporting!

@jcavar jcavar closed this as completed Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants