Repository navigation
Web pack issues when build in release mode #2716
Description
From @patrickpereira on April 12, 2017 4:56
Hi Nativescript,
I keep getting errors trying to upload the .ipa to itunes connect, what are the build.xcconfig settings and the command that should be used, currently I'm having this in build.xcconfig:
CODE_SIGN_IDENTITY = iPhone Distribution
DEVELOPMENT_TEAM = XXXXXXXX
OR
PROVISIONING_PROFILE = XXXXXXXX
I've tried both DEVELOPMENT_TEAM & PROVISIONING_PROFILE
If I'm using DEVELOPMENT_TEAM I get the following error from application loader:
ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle app.nurt.kcal [Payload/Kcal.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
If I'm using PROVISIONING_PROFILE, I'm unable to build it and get the following error from the CLI:
Check dependencies
Kcal has conflicting provisioning settings. Kcal is automatically signed, but provisioning profile XC iOS: app.nurt.kcal has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor, or switch to manual signing in the project editor.
Code signing is required for product type 'Application' in SDK 'iOS 10.2'
Code signing is required for product type 'Application' in SDK 'iOS 10.2'
Code signing is required for product type 'Application' in SDK 'iOS 10.2'
Code signing is required for product type 'Application' in SDK 'iOS 10.2'
I know the provisioning profile is valid, since I'm able to do the release through xcode if I compile the ipa there. But for some reason that ipa file is almost twice the size of the one created by the CLI.
The command I'm using in the CLI is: npm run build-ios-bundle -- --release --for-device
Furthermore I'm using tns-ios 2.5.
Hope you can help me ( @sis0k0 ) :-)
Copied from original issue: NativeScript/nativescript-dev-webpack#115
Activity
spike1292 commentedon Apr 19, 2017
We are experiencing the same issue. Now we need to use xcode to release. This means we need a manual step in our build process. This is very inconvenient for us.
patrickpereira commentedon Apr 20, 2017
@dtopuzov Any hints as to what is wrong?
dtopuzov commentedon Apr 20, 2017
Fixed in web pack plugin with this PR: NativeScript/nativescript-dev-webpack#116
We will release new version later today or tomorrow.
patrickpereira commentedon Apr 20, 2017
Amazing!!!
[-]Release mode errors[/-][+]Web pack issues when build in release mode[/+]dtopuzov commentedon Apr 20, 2017
Ups sorry, it looks I was wrong and my previous post was for another issue.
patrickpereira commentedon Apr 20, 2017
Yeah - I can see as I'm still getting the same error... But thanks for letting me know, a moment right there I thought my computer was just being weird :-)
PanayotCankov commentedon Apr 20, 2017
This PR is supposed to address this issue: #2705 There is some more work to be done though.
patrickpereira commentedon Apr 20, 2017
Thanks for letting me know @PanayotCankov! Is there a temporary fix that I can apply to get it working, as I'm just about to submit to itunes connect?
sis0k0 commentedon Apr 20, 2017
Hi @patrickpereira,
As a workaround you can do the following:
First, prepare the project for iOS using
tns prepare ios.Then, bundle the project with webpack with
webpack --config=webpack.ios.js --progress(note: if you don't havewebpackinstalled globally, you should add this to your package.json scripts or run webpack fromnode_modules/.bin/webpack).When the project is bundled and prepared in the
platforms/iosfolder, you can open it and release it through xcode.We'll add a way to perform the first two steps with
ns-bundleand then release the app through xcode later.feat(ns-bundle): app can be just prepared and bundled now
feat(ns-bundle): app can be just prepared and bundled now (#126)
33 remaining items
tjvantoll commentedon Jul 24, 2017
@dbenninger THANK YOU! 🌮
@PanayotCankov @sis0k0 @pkoleva Why is it necessary to add
<key>method</key><string>app-store</string>to yourInfo.plistto perform release builds that iTunes Connect accepts?We either need to workaround this on the CLI, or we need to get this on the documentation asap. I can help with the docs, but I need to know what we want to recommend here, and why this works the way it does.
Could the CLI handle this for us when with the
--releaseflag maybe?PanayotCankov commentedon Jul 31, 2017
Because this is broken:
nativescript-cli/lib/services/ios-project-service.ts
Line 262 in 1955028
We add the info.plist as plist for the export when building,
while the export accepts completely different format.
It is like a tool needs some data such as method = app-store in XML and we sticked the AndroidManifest.xml in it just in case.
PanayotCankov commentedon Jul 31, 2017
I have tried to elaborate on the problem here: #3020
alereisan commentedon Apr 5, 2018
I have the same problem, even after trying to publish with 'ad-hoc' or 'app-store' suggestions from above..
cerireyhan commentedon Jun 26, 2018
@alereisan Did you manage to solve this issue? I tried 'ad-hoc- and 'app-store' like you but I still have it.
alereisan commentedon Jun 26, 2018
@cerireyhan I solved it by making a new provisioning profile and certificate.