-
-
Notifications
You must be signed in to change notification settings - Fork 197
Error when we are publishing to AppStore #3470
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
Comments
+1 from #3479 |
+1 |
@elimin8r @nmongiya @xnramx @dbay920 are you guys hitting this issue with previous versions of NativeScript? @elimin8r @nmongiya if possible, please provide more details about your cases - including the exact command used to build the release IPA and the used versions of NativeScript CLI, |
I did a workaround...
If any error occurs the xcode will give you more information. |
@NickIliev I only tryed to publish with this NS version. |
In case when produced Info.plist is not a binary file, `tns publish ios` command fails because `bplist-parser` is not able to parse non-binary plist files. This PR replaces `bplist-parser` module with `sample-plist` that is able to parse binary and non-binary files. Fixes NativeScript/nativescript-cli#3470
In case when produced Info.plist is not a binary file, `tns publish ios` command fails because `bplist-parser` is not able to parse non-binary plist files. This PR replaces `bplist-parser` module with `sample-plist` that is able to parse binary and non-binary files. Fixes #3470
Hi guys, We've investigated the error from |
Will be shipped officially with 4.0 next week. |
Tell us about the problem
When I run the following command:
tns publish ios <Apple ID> <Password> <Mobile Provisioning Profile Identifier> <Code Sign Identity>
an error is thrown:
I've already tryed to publish by Sidekick but the error is not clear too.
Which platform(s) does your issue occur on?
iOS
Please provide the following version numbers that your issue occurs with:
Info.plist:
.entitlements:
build.xcconfig:
The text was updated successfully, but these errors were encountered: