-
Notifications
You must be signed in to change notification settings - Fork 46
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
ionic cordova resources command fails #45
Comments
The plugin "just" calls out to the If you post your complete output, I might be able to see which of their commands is doing this and find out if they have a param that disables this behavior - and add it to the plugin. |
I added full output: $ fastlane ios beta [18:19:32]: fastlane detected a Gemfile in the current directory [18:19:32]: however it seems like you don't use `bundle exec` [18:19:32]: to launch fastlane faster, please use [18:19:32]: [18:19:32]: $ bundle exec fastlane ios beta [18:19:32]: [18:19:32]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile +-------------------------------------+---------+--------------------------------------+ | Used plugins | +-------------------------------------+---------+--------------------------------------+ | Plugin | Version | Action | +-------------------------------------+---------+--------------------------------------+ | fastlane-plugin-cordova_screenshots | 0.2.0 | init_cordova_screenshots_ios | | | | retrofit_cordova_screenshots_android | | | | retrofit_cordova_screenshots_ios | | | | init_cordova_screenshots_android | | fastlane-plugin-ionic | 0.1.0 | ionic | +-------------------------------------+---------+--------------------------------------+ |
Ok, that seems to happen during the
So |
You might try to run |
I use ionic command to build my app with this parameters:
But somehow this is calling
ionic cordova resources
command and it fails.Is this part of this plugin? Can I skip this step? Because I manage creating resources manually.
The text was updated successfully, but these errors were encountered: