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

iOS build error #100

Open
ahmednaxim opened this issue Apr 9, 2020 · 3 comments
Open

iOS build error #100

ahmednaxim opened this issue Apr 9, 2020 · 3 comments

Comments

@ahmednaxim
Copy link

Hi, I am using PhoneGap build to compile the application. I am trying to use this plugin to associate a simple text file with the App. I am developing the app for iOS and Android.
It successfully builds for Android, but it shows the following build error for iOS.

Error - The following 3rd-party plugin is causing the build to fail and may need to be updated to a newer version: cc.fovea.cordova.openwith.

And in the iOS build log it shows the following error:
........myAppname.build/Objects-normal/armv7/OpenWithPlugin.o /project/myAppname/Plugins/cc.fovea.cordova.openwith/OpenWithPlugin.m:2:9: fatal error: 'ShareViewController.h' file not found #import "ShareViewController.h" ^~~~~~~~~~~~~~~~~~~~~~~ 1 error generated.

In the config.xml, I am using the following:
<plugin name="cordova-plugin-openwith" spec="https://github.com/j3k0/cordova-plugin-openwith.git"> <param name="ANDROID_MIME_TYPE" value="text/plain" /> <!-- iOS --> <param name="IOS_URL_SCHEME" value="myAppUniquename" /> <param name="IOS_UNIFORM_TYPE_IDENTIFIER" value="public.data" /> <param name="IOS_GROUP_IDENTIFIER" value="group.myAppId" /> <param name="SHAREEXT_PROVISIONING_PROFILE" value="bcc........." /> <param name="SHAREEXT_DEVELOPMENT_TEAM" value="S12233444" /> </plugin>

@HarelM
Copy link
Contributor

HarelM commented Jul 23, 2020

@ahmednaxim did you manage to fix this or find a workaround?

@muratclk
Copy link

Did you fix it :D

@HarelM
Copy link
Contributor

HarelM commented Feb 19, 2021

I found a and delivered a fix for it sometime ago, I think, see d6a2bf2
Try using the latest version from this repo instead of the npm version.

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