I am trying to build my normal package using Ionic Cloud and getting this error for iOS (Android is fine):
Anyone know what this means?
The following build commands failed:
Check dependencies
(1 failure)
Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/package/workspace/apps-0faa2935-462/cordova/platforms/ios/cordova/build-release.xcconfig,-workspace,QueMesa.xcworkspace,-scheme,QueMesa,-configuration,Release,-destination,generic/platform=iOS,-archivePath,QueMesa.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/package/workspace/apps-0faa2935-462/cordova/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/package/workspace/apps-0faa2935-462/cordova/platforms/ios/build/sharedpch
Most likely thereâs a conflict with one of your plugins, your Apple Certificate is not configured correctly, or your platformâs config.xml does not include a plugin that it should include.
Also, when I get error 65 for iOS itâs usually because I donât have Xcode signing configured properly. Open up in Xcode and double check that the signing singatures are correct.
Hmm - I had to downgrade back to app-scripts 2.1.4 because 3.0 did not recognise our Environment file (additional build actions). However I will try it anyway and see if that fixes it.
Ok thanks - weâve tried rolling back to an older version that did work and it is also failing strangely. The certificates havenât changed since the last succesful build (2 weeks earlier) but I will double check.
I noticed some plugins for iOS have changed in one of the new Ionic releases - I will investigate - at this point not having much luck narrowing down the problem.
Itâs really odd. I went back to my master branch to the last released version that was successful and delete the NodeModules folder and ran npm -i. It still fails (this built successfully 2 weeks ago). I repeated the test on a different computer with the same result.
This leads me to think it is either
Ionic Cloud Package has changed since October 12 (last successful iOS Cloud build)
One of my global dependacies has been updated.
I then updated Ionic Scripts, Ionic CLI and Cordova all to the latest so my Ionic Info file looks like this:
cli packages: (C:\git\QueMesaMobile\node_modules) @ionic/cli-utils : 1.15.2
ionic (Ionic CLI) : 3.15.2
Good point! Itâs a different error now - something has run out of space! Itâs not my harddrive so I think it might be something on Ionic Package service? (this is the build output from https://apps.ionic.io/app/xyz/package, not from my command window)
Discovered plugin âcordova-plugin-google-analyticsâ in config.xml. Adding it to the project
shell.js: internal error
Error: ENOSPC: no space left on device, write
at Error (native)
at Object.fs.writeSync (fs.js:788:20)
at copyFileSync (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/src/cp.js:34:8)
at cpdirSyncRecursive (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/src/cp.js:82:9)
at /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/src/cp.js:180:9
at Array.forEach (native)
at Object._cp (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/src/cp.js:157:11)
at Object.cp (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/src/common.js:186:23)
at copyPlugin (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/fetch.js:376:15)
at /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/fetch.js:233:28
I was having this problem earlier. It seems to be failing at some other part of the process now,
** ARCHIVE FAILED **
The following build commands failed:
Ld /Users/package/Library/Developer/Xcode/DerivedData/Sippin-apsqnitpryjqthcronpsavfjfxik/Build/Intermediates/ArchiveIntermediates/Sippin/IntermediateBuildFilesPath/Sippin.build/Debug-iphoneos/Sippin.build/Objects-normal/armv7/Sippin normal armv7
(1 failure)
Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/package/workspace/apps-8b589aec-396/cordova/platforms/ios/cordova/build-debug.xcconfig,-workspace,Sippin.xcworkspace,-scheme,Sippin,-configuration,Debug,-destination,generic/platform=iOS,-archivePath,Sippin.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/package/workspace/apps-8b589aec-396/cordova/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/package/workspace/apps-8b589aec-396/cordova/platforms/ios/build/sharedpch
The package build seems to have been buggy all day.
I am led to believe this is a server-side issue because scrolling up in the logs shows the initial point of error:
ld: framework not found IOSurface for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
P.S. My last successful cloud build was on October 19.
Now my error is:
âSwift Language Versionâ (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift SyntaxâŚ] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.
The problem is the GeoFence plugin on iOS. It was working fine on the 13th of October and before (the current live version of QueMesa.com uses GeoFencing in iOS. However I canât get it to build now.
I have tried installing âcordova-plugin-add-swift-supportâ plugin and setting
Yes, I am using a different geo-based plugin on iOS. I canât get mine to build now either. Iâm wondering if there has been something really strange with their build environment going on lately. My thoughts are that:
Apple updated something between October 19 and Oct 27, and/or
Ionic has not yet updated their package build services, or
That StackOverflow indicates that there is some framework missing from the build environment, as is supported by my error logs. Are you still having your issue?
Yes, we cannot release our product app due to this and cannot find a solution.
The last successful build for us October 12 (although we did not try an iOS build again until the 19th when it failed).
Weâre going to try a few things today and I will report back.
We might need some assisitance from the Ionic Core Team on this.
Iâm in the same boat, Rodney. I cannot release some core updates due to this and since I am very sure it is on their backend, can do nothing about it. I donât develop on a Mac so there is no way for me to build the iOS update.
I have had a ticket in with the Ionic Support Team for 4 days and have heard nothing back on this issue. This is very frustrating. Nor have I heard back from them (even to indicate they are working on it) besides the initial response that the ENOSPC error should be fixed.
Ok, weâve done some more fiddling and we think this is what has happened:
The Ionic Cloud build was upgrade to use a newer version of Xcode which uses Swift 3 (around the 19th of October or a few days before)
The GEOFencing plugin needs to use Xcode 8.2 which is compatible with Swift 2.3. It does not work with Swift 3
Therefore the build returns errors saying that the GEOFencing plugin cannot be used
Possible Solutions:
Use a flag to tell Ionic Package to use Xcode 8.2 so we can use the existing plugin as before
Get the Cordova Plugin updated so that it works with Swift 3
I am appealing to the GeoFence creator to work on Point 2 but they obviously have their own time and schedules (I have no idea to update it to Swift 3)
I would really like some guidance from the Ionic Core Team if my observations are correct to understand if there solutions and the best way forward or not. Ie. Was something changed in the Ionic Cloud Build around the 19th of October, and if so, what was it? Thanks
Iâm coming to the same conclusion. I have spent the past few hours gruelingly updating all my packages and accounting for changes (I was a few versions behind, just in case that was the problem) to no avail. Still failing with cloud build, and we are dependent on using ionic package for our iOS builds.
The lack of transparency is definitely frustrating. For me, it seems like there is just a missing framework.
Also, I spoke with the developer of my plugin, and he says that the framework IS Swift 3 compatible. So Swift 3 is not the issue, but rather it seems that when using the âlink frameworks automaticallyâ flag that is causing an issue.
Furthermore, the developer of my plugin says that IOSurface IS an IOS 11 API, so in my case their package build services are actually behind. Perhaps they are working on Xcode 8.3 and that is why it is working for neither of us. I am completely sure this is an issue with their build services though, and not our builds.
I had the clever thought of setting<preference name="deployment-target" value="11.0" /> since IOSurface is an IOS 11 (and backdated to 10) API. However after setting this preference, we can see the SAME error setting up on the build environment.
This is from a different build packaging company but at least I know why mine is failing. They must have updated or reverted something on or around that date to cause your build failure.
