-
-
Notifications
You must be signed in to change notification settings - Fork 197
fix: CFBundleName cannot be changed #5427
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
fix: CFBundleName cannot be changed #5427
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks lika a reasonable fix to me - however I wonder if this is ever called before any .ipa
exists in the output folder - in those cases, this might fail.
Does running a custom CFBundleName
on device work after running ns clean
in a project? That would likely be sufficient to confirm if this will work or not!
Perhaps we could fall back to ${projectData.projectName}.ipa
if ipaFileName
is empty.
lib/services/ios-project-service.ts
Outdated
this.$fs.readDirectory( | ||
this._platformData.getBuildOutputPath(buildOptions) | ||
), | ||
(directory) => path.extname(directory) === ".ipa" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(directory) => path.extname(directory) === ".ipa" | |
(entry) => path.extname(entry) === ".ipa" |
Minor suggestion, since we are not strictly dealing with directories.
After running |
PR Checklist
What is the current behavior?
After changing CFBundleName in Info.plist, the app is built, but can't be installed because of missing .ipa file.
What is the new behavior?
App is built, installed and started, respecting the CFBundleName.
Fixes #5424