-
Notifications
You must be signed in to change notification settings - Fork 7
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
Native linking failed error when building for device #5
Comments
Cheers for the tip. Is this reproducible with the attached storyboard example? If so I'll have a look at it probably tomorrow and add it in or if you could submit a pull request, that'd also be great. |
It only happens when building for a device and I don't have a provisioning profile for that project. I could probably make one, but Apple doesn't make that easy for us... I did try to send a pull request but was not able to get it through. I'm probably not doing it right though - I've never created a pull request before. This is the only change that is needed in ApiDefinition.cs (just add "Protocol" in there):
I've done that locally and it fixes the linker problem and everything works great. Thanks for the follow-up and for putting this binding together. It works great and saved me alot of time! |
No problem. I'll verify the bug as soon as I can and get the project updated. Thanks again for informing the bug with the fix :)
That goes out to Jesper :) I'm just maintaining the project since he's not working with Xamarin currently. |
With the latest Xamarin iOS beta (7.2.2.2), I'm getting a Native linking failed error related to the SWRevealViewControllerDelegate class when I deploy to a device. To fix it, we need the Protocol attribute added to that interface definition.
The text was updated successfully, but these errors were encountered: