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

Version 2.0.0 seems to ignore the name config.xml value #11

Open
morungos opened this issue Mar 27, 2016 · 3 comments
Open

Version 2.0.0 seems to ignore the name config.xml value #11

morungos opened this issue Mar 27, 2016 · 3 comments

Comments

@morungos
Copy link

When I used 2.0.0 the output platforms/ios directory doesn't pick up the app name, and I get a HelloCordova app. Reverting back to 1.1.0 resolves the issue.

@morungos
Copy link
Author

My bad, it's a weird timing thing with my gulpfile.js. And reverting doesn't help reliably, although it seemed to once.

@morungos
Copy link
Author

I'm reopening, because it doesn't seem to be a clean timing issue, but it's probably an issue with the version of cordova-lib. My task is roughly:

gulp.task('cordova', ['package-cordova'], function() {
  return gulp
    .src('.cordova', {read: false})
    .pipe(ios())
});

Where a lot of magic happens in package-cordova. When done, everything seems to be good, and when cordova-lib <= 6.0.0, all works fine. When run with cordova-lib == 6.1.0, you get:

[13:03:17] Starting 'cordova'...
add to body class: platform-ios
cp: copyFileSync: could not write to dest file (code=ENOENT):/Users/stuart/git/myproject/.cordova/platforms/ios/Turalt/config.xml

[13:03:26] 'cordova' errored after 8.95 s
[13:03:26] Error in plugin 'gulp-cordova-build-ios'
Message:
    ENOENT: no such file or directory, open '/Users/stuart/git/myproject/.cordova/platforms/ios/Turalt/config.xml'

This is because whatever is being done in cordova-lib isn't creating a platform application Turalt, but instead a project HelloCordova, despite the <name> in config.xml being present and correct. It is possible that this is a [email protected] issue, but whatever it is, it's a broken combination.

@morungos morungos reopened this Mar 27, 2016
@SamVerschueren
Copy link
Owner

Alright, will have a look at it. Ping me back if you haven't heard of me in a couple of days.

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

2 participants