andycwk commented on issue #536: Provisioning Profile not setup correctly with 
new build system
URL: https://github.com/apache/cordova-ios/issues/536#issuecomment-551173111
 
 
   Hay Peeps,
   
   So... I've been having the same issue where my release build was not 
building as it was trying to use the dev time cert  (and banging head on wall 
for a week or so)
   
   I've now pined down the culprit, at least for my use case thanks to this 
thread, but writing it up here incase it helps anyone else in the same bucket 
of crud!
   
   Basically I have an Ionic 3 build that was working until I updated 
cordova-ios (5.0.1) to the latest version (may have also updated 
branch-cordova-sdk (version 3.2.0) but can't remember of the top of my head)
   
   While 
https://github.com/BranchMetrics/cordova-ionic-phonegap-branch-deep-linking-attribution/pull/577/files
 has not been merged, I've been able to identify it as a fix locally by 
modifying my `node-package` scripts.
   
   As a fix for now.. I have stored the modified version of the 
`enableEntitlements.js` script and add the following in my beta fastlane to 
`hack` around the issue until something better is in place!
   
   ```
   FileUtils.cp_r '../resources/branh-enableEntitlements.js', 
'../node_modules/branch-cordova-sdk/src/scripts/ios/enableEntitlements.js'
   FileUtils.remove_dir '../platforms', true
   FileUtils.remove_dir '../plugins', true
   sh "(cd .. && ionic cordova build ios -- 
--buildConfig='#{ENV['BITRISE_CORDOVA_BUILD_CONFIGURATION']}' 
--buildFlag='-UseModernBuildSystem=0' --device --release --verbose)"
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to