You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a comment for anyone who ran into the "Use of undeclared..." issue that was previously closed (#9 ). I was still getting that message even after the bridging header was set properly. Also, right click and "jump to definition" always returned a "?" for any methods inside the WebRTC framework.
I solved it by renaming the project in Xcode from "WebRTC" to "WebRTC-add-your-own-value".
I suspect that references inside the WebRTC framework could not be linked properly because the project name and the framework name are the same, creating ambiguity. Anyways, this is just a guess since now everything works correctly and I am able to jump to definitions inside the framework.
@stasel once you figure out the exact reason why this was happening, I would suggest a feature request to rename this project to something other than WebRTC.
The text was updated successfully, but these errors were encountered:
Hi @Sovenger, Thank you for pointing this out.
I had problems reproducing this issue as it was working well on my machine, even with a clean clone. However, I managed to reproduce this today and indeed the issue was resolved once I have changed the project name. It wasn't a good idea to call the project WebRTC too just like the framework.
I have rename the WebRTC to WebRTC Demo and you can see already the updates in the master branch.
This is more a comment for anyone who ran into the "Use of undeclared..." issue that was previously closed (#9 ). I was still getting that message even after the bridging header was set properly. Also, right click and "jump to definition" always returned a "?" for any methods inside the WebRTC framework.
I solved it by renaming the project in Xcode from "WebRTC" to "WebRTC-add-your-own-value".
I suspect that references inside the WebRTC framework could not be linked properly because the project name and the framework name are the same, creating ambiguity. Anyways, this is just a guess since now everything works correctly and I am able to jump to definitions inside the framework.
@stasel once you figure out the exact reason why this was happening, I would suggest a feature request to rename this project to something other than WebRTC.
The text was updated successfully, but these errors were encountered: