-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Compile error in Swift code #101
Comments
oh, interesting. Does everything work smoothly if you add an override keyword to that function? |
Thanks for the quick response! I thought of trying what you suggested, but unfortunately there's no easy way for me to make that change. Since I have to use Expo's EAS build, which is a cloud service, the only way I can add modules is through NPM. So for me to test that, I would have to clone, make the change, and publish a private NPM module which I'm not really setup to do. How hard would it be for you to publish a version with this fix so I can test it? Also, I looked in the logs and noticed it was using version 15 of the the iOS SDK, and version 5.4 of Swift. So maybe you could try a build beforehand using those versions and confirm if you can reproduce the error and if adding the override keyword fixes the problem. |
I ran into this same issue, and was able to hack together a fix by updating the override keyword and proxying NPM locally with verdaccio |
Same error. Unable to build. |
Any progress on this? More info:
|
@mdhaney Hi, I know that the thread is not very recent, but since I'm trying to implement this package on expo I wonder if you could kindly share the code of the plugin you used. |
Bug
Describe the bug
I'm trying to use the library in an Expo project using their EAS build tool (which lets you add third party native modules) and I get the following error while compiling the pod:
Any idea why I could be getting this error? Do I need to be compiling against a certain version of the iOS APIs or something like that? Thanks for any help, because I really need to get this working.
The text was updated successfully, but these errors were encountered: