[
https://issues.apache.org/jira/browse/CB-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261727#comment-16261727
]
Colin Bau edited comment on CB-13595 at 11/22/17 2:27 AM:
----------------------------------------------------------
hi [~surajpindoria]
thanks your reply
if you fix your provisioning profiles later，please help me to try and build
again to see if fix...
because I really check many times with my provisioning profiles，really no
problem at all
maybe build.json have some problem，if you have free time，please help me to
check it
[click me to download my
project|http://www.littlebau.com/ios/framework7_full.rar]
let me explain why it show /Volumes/ directory
My Mac OS is a VM System
I am not a Mac OS user but only a Windows user，I am just use Mac OS to build
iOS application
my project "framework7" is in my PC's => D:\software\Cordova\framework7
I launch my VM，login to my "framework7" project，enter my PC's password
finally drag the "framework7" folder to the Mac OS commandline
above workflow that I am sure is OK
because I am not the first time to upload ipa to app store
detail screenshot all under here
!https://www.littlebau.com/ios/volume/01.png!
!https://www.littlebau.com/ios/volume/02.png!
!https://www.littlebau.com/ios/volume/03.png!
was (Author: bau720123):
hi [~surajpindoria]
thanks your reply
but [~Sujan12] said︰If you get the same error without `--release` it means this
has nothing to do with profiles and certificates - much simpler to debug.
so...
who's explanation is correct ? it really A little confusion @_@
could I request [~surajpindoria] and [~Sujan12]
just use my sample project (a default [email protected] project)
[click me to download|http://www.littlebau.com/ios/framework7_full.rar]
or create your own [email protected] project
then...
use your own Provisioning Profiles or certificates or build.json file to build
the project to success ?
no matter which way...
cordova build ios --device => (*{color:red}+for now we are tryng for
this+{color}*)
or
cordova build ios --device --release
by the way [~surajpindoria]
if I manually use Xcode to build，it will build success and generate a ipa file
finally
https://www.littlebau.com/ios/step3/01.png
https://www.littlebau.com/ios/step3/02.png
> cordova build ios --device --release not work
> ---------------------------------------------
>
> Key: CB-13595
> URL: https://issues.apache.org/jira/browse/CB-13595
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Affects Versions: cordova-ios 4.5.0
> Environment: cordova -v︰7.1.0
> node -v︰8.9.1
> Xcode 9.1(9B55)
> cordova ios︰4.5.3
> macOS High Sierra 10.13
> Reporter: Colin Bau
> Assignee: Suraj Pindoria
> Labels: ios
>
> step 1
> I import my Provisioning Profiles to keychain (double click)
> !https://www.littlebau.com/ios/step1/01.png!
> !https://www.littlebau.com/ios/step1/02.png!
> step 2
> I prepare the build.json file (I tried the older format and new format but
> still no luck)
> I am very sure the "provisionProfile" is correct (it was my
> provisionProfile's UUID)
> [link
> title|https://cordova.apache.org/docs/en/latest/guide/platforms/ios/#using-buildjson]
> !https://www.littlebau.com/ios/step2/01.png!
> !https://www.littlebau.com/ios/step2/02.png!
> step 3
> I use Xcode and setting the Signing，it will build success
> !https://www.littlebau.com/ios/step3/01.png!
> !https://www.littlebau.com/ios/step3/02.png!
> step 4
> but if I use︰cordova build ios --device --release
> it will "ARCHIVED FAIL"
> !https://www.littlebau.com/ios/step4/01.png!
> !https://www.littlebau.com/ios/step4/02.png!
> !https://www.littlebau.com/ios/step4/03.png!
> in previous cordova-ios version，above workflow is work perfect and it will
> generate a ipa format file finally
> but in new cordova-ios or Xcode version，it seem not work anymore
> if I miss something or give me some hint to solve it ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
