I upgraded from xcode 10.1 to xcode 10.2.1. I needed to change a zendesk pod to satisfy swift 5. This builds fine locally but when travis CI tries to run this command from travis.yml file:
set -e
./.travis/scripts/setup_profiles.sh
./.travis/scripts/deploy_beta.sh "${WORKSPACE}" "${SCHEME}" "${TRAVIS_BUILD_NUMBER}"
set +e
I am getting an error and this is from the raw logs:
⌠error: Multiple commands produce '/Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework':
⌠error: Multiple commands produce '/Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleUtilities.framework':
unexpected mutating task ('SetOwnerAndGroup travis:staff /Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework') with no relation to prior mutator ('SetOwnerAndGroup travis:staff /Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework') (in target 'nanopb-iOS11.0')
unexpected mutating task ('SetMode u+w,go-w,a+rX /Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework') with no relation to prior mutator ('SetMode u+w,go-w,a+rX /Users/travis/build/xxx/mobile-ios/.build/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework') (in target 'nanopb-iOS11.0')
The problem was that I had duplicate frameworks. After deleting the dupes, the CI ran fine.
Related
Helpppp ! I just want to get my pipeline run successfully T.T Anyone can help me here~
Situation: I am integrating Apollo client in my iOS project and following the instruction provided by official Apollo - https://www.apollographql.com/docs/ios/installation (using SPM way to setup). It works all fine for me in Xcode manual compile and testing. However, when I am using the command to run the unit test, I got stuck while generating Apollo GraphQL API. Below is the error I have received while running
xcodebuild test -scheme ${CI_PROJECT_NAME} -project ${CI_PROJECT_NAME}.xcodeproj -destination "${XCODE_APPLICATION_PLATFORM}" -enableCodeCoverage YES| xcpretty -s
Error: xcodebuild[10347:2192409] NSFileHandle couldn't write. Exception: *** -[_NSStdIOFileHandle writeData:]: Broken pipe
Note: This error occurs while I am running unit test through command line in Gitlab pipeline. Using Xcode 13.2.1.
Testing failed:
CoreAppTests:
CoreApp.app (10848) encountered an error (Early unexpected exit, operation never finished bootstrapping -
no restart will be attempted. (Underlying error: Crash: CoreApp (10848): Namespace SPRINGBOARD, Code 0x8badf00d))
After updating my Mac mini OS to latest and XCode to 11.1 getting the error message. I'm running test cases for an IOS app using Jenkins and Sonar Qube, build is happening perfectly but test cases are not getting executed. Even sometimes i'm getting the following error, and after that the job fails.
Finished requesting crash reports. Continuing with testing - Jenkins
I even downgraded my XCode back to 10.3 but the issue is still there.
Cannot even build in sidekick after a simple change
I created a new Core/TS project in Sidekick, I built the app and developed some stuff, but later I changed the icon to a nicer one (which requires a new build, no HMR for this type of change obviously), now I cannot build my app (cloud build, because I don't have Android Studio).
I checked the /main/assets/app/ and the icons were successfully changed there and they were existed.
What is happening? How do I fix this big issue? My patience bottle with all these critical errors even after simple changes is getting emptied.
I also tried "removing .cloud and folder directories", and clicking "clean cloud processes", adding "clean" option, etc...
But none worked.
I also updated the webpack.config.js file, with node_modules.bin\update-ns-webpack --configs
The file got successfully updated, but still did not solve the problem and I still cannot build.
Still after many hours cannot cloud build my app in sidekick. I also tried tns platform remove android, tns install, etc, etc... none worked out.
this is the error message:
[00:00:18.521] [WARN] Executing webpack failed with exit code 2.
[00:00:18.681] [ERROR] clean-webpack-plugin: /mnt/storage/builds/_/af8fe992d35e76b54f5523261a83dac973ffc9ed/5.3.4/5.3.1/Spread/platforms/android/app/src/main/assets/app/**/* has been removed.
Executing webpack failed with exit code 2.
'Build failed with error code 2'.
[19-06-10 19:13:56.767] Couldn't enable debugging for EP7333JKFA, Error: Couldn't enable debugging for EP7333JKFA
at Errors.fail (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:126:28)
at Errors.failWithoutHelp (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:136:21)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:253:30)
at Generator.next (<anonymous>)
at C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:13:71
at new Promise (<anonymous>)
at __awaiter (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:9:12)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:250:16)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\decorators.js:67:47)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:290:25)
at Generator.next (<anonymous>)
at fulfilled (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:10:58)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
OUTPUT 2
EDIT:
SOLVED
https://github.com/NativeScript/sidekick-feedback/issues/384#issuecomment-508028462
I know this isn't an answer, but it is happening to me, too. I am running Nativescript 5.4.1. I can build with webpack, but as soon as I try to run with AOT or Uglify, I can't build and the error message isn't very helpful.
Try to remove and add 'nativescript-dev-webpack'-plugin using nativescript-sidekick-GUI, this resolve my issue...
I am trying to run my existing code from one system to another and facing continue following error :
bundle format unrecognized, invalid, or unsuitableCommand
/usr/bin/codesign failed with exit code 1
How to resolve this error ? I didn't change a single line of code. However in my existing system, its working like a charm. Any hep appreciate.
This is the error you are getting because of some system settings changed. You can solve it by following below steps :
This error will say for which pod you are facing this issue. So select that pod file.
Now select Target for that Pod
Now got To General
Tap on Choose info.plist File
It will show you pods-yourprojectnae-acknowledgements.plist, so select that option
Now Build and check
you will not find this error again
This solution works for me. Try once.
I'm getting the following error in LogDNA:
(node:28) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Cannot find module '/tmp/build_[long-hash]/my-project-[long-hash]/node_modules/bluebird'
Process exited with status 0
State changed from starting to crashed
That line contains an import of Bluebird. When I remove the dependency and remove the line, then I get the same error, except it references the next line (which is also a dependency import).
When I deploy a branch that was previously working, I get the same error. Of course, I cannot re-pro this issue locally.
I compared the Dyno's npm list against my local, and they're the same. Also, all of the expected node_modules are, in fact, present in the Dyno's filesystem.
If I use Heroku-bash run the build task manually (with nothing special), then deploy, it's fine.
We had hard-coded/fixed the version of Electrode we're depending on, but Electrode has a fuzzy version for WebPack, which released a new version 5 days ago that caused this error. It causes the imports' paths to be incorrectly resolved/transpiled to the build directory instead of remain relative.
The workaround is to use require() instead of import.