I am using the Twilio Voice iOS library with Xamarin
As of now, it's beta version 19.
I'm using this command
sharpie bind -output TwilioBeta19 -namespace TwilioBeta19 -sdk iPhoneOS10.3 /Users/lamont/Desktop/TwilioVoiceFramework/TwilioVoice.framework/Headers/*.h -scope /Users/lamont/Desktop/TwilioVoiceFramework/TwilioVoice.framework/Headers -c -F .
With this error, and output:
Question, how do I solve the error below?
Parsing 6 header files... In file included from /var/folders/c6/w2rvd7zj0mx14pggh517lbb80000gn/T/tmp6a160417.h:1: /Users/lamont/Desktop/TwilioVoiceFramework/TwilioVoice.framework/Headers/TVOCall.h:8:9: fatal error: 'Foundation.h' file not found #import <Foundation.h> ^~~~~~~~~~~~~~ Binding... [write] ApiDefinitions.cs [write] StructsAndEnums.cs Binding Analysis: Automated binding is complete, but there are a few APIs which have been flagged with [Verify] attributes. While the entire binding should be audited for best API design practices, look more closely at APIs with the following Verify attribute hints: ConstantsInterfaceAssociation (1 instance): There's no foolproof way to determine with which Objective-C interface an extern variable declaration may be associated. Instances of these are bound as [Field] properties in a partial interface into a nearby concrete interface to produce a more intuitive API, possibly eliminating the 'Constants' interface altogether. MethodToProperty (1 instance): An Objective-C method was bound as a C# property due to convention such as taking no parameters and returning a value (non-void return). Often methods like these should be bound as properties to surface a nicer API, but sometimes false-positives can occur and the binding should actually be a method. PlatformInvoke (5 instances): In general P/Invoke bindings are not as correct or complete as Objective-C bindings (at least currently). You may need to fix up the library name (it defaults to '__Internal') and return/ parameter types manually to conform to C calling conventionsfor the target platform. You may find you don't even want to expose the C API in your binding, but if you do, you'll probably also want to relocate the definition to a more appropriate class and expose a stronger type-safe wrapper. For P/Invoke guidance, see http://www.mono-project.com/docs/advanced/pinvoke/. Once you have verified a Verify attribute, you should remove it from the binding source code. The presence of Verify attributes intentionally cause build failures. For more information about the Verify attribute hints above, consult the Objective Sharpie documentation by running 'sharpie docs' or visiting the following URL: http://xmn.io/sharpie-docs 1 error generated. Error while processing /var/folders/c6/w2rvd7zj0mx14pggh517lbb80000gn/T/tmp6a160417.h. Done. Exiting with error code 1. error: Clang failed to parse input and exited with code 1 macos:~ lamont$