I have read a lot of articles, but still not resolved, who can help me
here is the problem I encountered with iOSOpenDev and I use xcode5.0.1
Preparing to run Xcode Build Phase...
Signing /Users/liu/Library/Developer/Xcode/DerivedData/SpeedBoy-agqiwpedazizphbbdcgogvekvdya/Build/Products/Release-iphoneos/SpeedBoy with ldid... 2014-02-19 12:39:50.818 xcodebuild[513:d0b] [MT] PluginLoading: Required plug-in compatibility UUID 37B30044-3B14-46BA-ABAA-F01000C27B63 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XEP.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2014-02-19 12:39:50.824 xcodebuild[513:d0b] XcodeColors: load (v10.1)
2014-02-19 12:39:50.827 xcodebuild[513:d0b] XcodeColors: pluginDidLoad:
2014-02-19 12:39:50.855 xcodebuild[513:d0b] Could not fetch 'View' main menu item Done.
Copying /Users/liu/Library/Developer/Xcode/DerivedData/SpeedBoy-agqiwpedazizphbbdcgogvekvdya/Build/Products/Release-iphoneos/SpeedBoy to package directory at /Users/liu/Desktop/SpeedBoy/SpeedBoy/Package/System/Library/WeeAppPlugins/SpeedBoy.bundle...
Preparing to build package...
Setting control file /Users/liu/Desktop/SpeedBoy/SpeedBoy/Package/DEBIAN/control Version field to 1.0-1 using /Users/liu/Desktop/SpeedBoy/SpeedBoy/PackageVersion.plist... Done.
Building package ... Done.
Creating zip /Users/liu/Desktop/SpeedBoy/Packages/com.SpeedBoy_1.0-1_iphoneos-arm.zip... Done.
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password,keyboard-interactive).
Failed to create directory /var/root/iOSOpenDevPackages on device 192.168.88.146
Command /bin/sh failed with exit code 255
Related
I'm using xcodebuild with the -workspace . option to build a Swift Package (a framework) for iOS (swiftbuild only builds for MacOS) in a Github Action. It works for all of our packages, except 2, where we get the error
xcodebuild: error: The workspace named "MyFramework" does not contain a scheme named "MyFramework". The "-list" option can be used to find the names of the schemes in the workspace.
But if I add xcodebuild -workspace . -list to the start of the build script, it shows that the scheme exists.
Anyone have an idea why it can't see the scheme that clearly is there, and what we can do to fix our script so this won't happen?
PS - This script runs fine locally.
Full build log:
xcodebuild -workspace . -list
2022-07-28 11:51:00.798 xcodebuild[2020:7121] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-07-28 11:51:00.799 xcodebuild[2020:7121] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
Command line invocation:
/Applications/Xcode_13.4.1.app/Contents/Developer/usr/bin/xcodebuild -workspace . -list
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
Resolve Package Graph
Fetching from git#github.com:me/aaa.git
Fetching from git#github.com:me/bbb.git
Cloning local copy of package ‘aaa’
Checking out 2.1.2 of package ‘aaa’
Cloning local copy of package ‘bbb’
Checking out 10.1.0 of package ‘bbb’
Resolved source packages:
MyFramework: /Users/runner/work/MyFramework/MyFramework
aaa: git#github.com:me/aaa.git # 2.1.2
bbb: git#github.com:me/bbb.git # 10.1.0
Information about workspace "MyFramework":
Schemes:
MyFramework
set -o pipefail && xcodebuild -configuration Debug -derivedDataPath .derivedData -destination platform='iOS Simulator,name=iPhone 12,OS=latest' -scheme MyFramework -workspace . build | xcbeautify
2022-07-28 11:51:38.874 xcodebuild[3034:9866] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-07-28 11:51:38.875 xcodebuild[3034:9866] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-07-28 11:51:50.008 xcodebuild[3034:9866] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-20504/IDEFoundation/Execution/RunContextManager/IDERunContextManager.m:823
Details: Error deleting scheme: Cannot modify data because the process disallows saving.
Object: <IDERunContextManager: 0x60000399aac0>
Method: -deleteRunContexts:completionQueue:completionBlock:
Thread: <_NSMainThread: 0x600001eac3c0>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2022-07-28 11:51:50.009 xcodebuild[3034:9866] could not delete old scheme: Error Domain=DVTCustomDataStoringErrors Code=0 "Cannot modify data because the process disallows saving." UserInfo={NSLocalizedDescription=Cannot modify data because the process disallows saving.}
xcodebuild: error: The workspace named "MyFramework" does not contain a scheme named "MyFramework". The "-list" option can be used to find the names of the schemes in the workspace.
Resolve Package Graph
make: *** [build-ios] Error 65
Resolve Package Graph
Resolved source packages
aaa - git#github.com:me/aaa.git # 2.0.1
bbb - git#github.com:me/bbb.git # 10.1.0
Error: Process completed with exit code 2.
I may have found a workaround (since I thought the same thing back when I adjusted the Xcode version, I'm not willing to commit just yet 😅):
Given the error message xcodebuild[3034:9866] could not delete old scheme: Error Domain=DVTCustomDataStoringErrors Code=0 "Cannot modify data because the process disallows saving.", I wondered if maybe the current directory is not writable, and changed the code to use the runner's temp directory in the Makefile:
ifeq ($(origin RUNNER_TEMP),undefined)
DERIVED_DATA_PATH=.derivedData
else
DERIVED_DATA_PATH="$(RUNNER_TEMP)/derivedData"
endif
...
xcodebuild -configuration Debug -derivedDataPath "$(DERIVED_DATA_PATH)" ...
This seems a bit inconsistent though, since it sometimes worked with .derivedData in the current directory. But then again, maybe something somewhere changes the current directory to a writeable directory occasionally, and that hid the bug ...
I have updated Xcode to Version 13.4.1 (13F100),
Then tried to run a flutter project
Launching lib/main.dart on iPhone SE (3rd generation) in debug mode...
Xcode build done. 2.9s
Failed to build iOS app
Error output from Xcode build:
↳
2022-06-11 12:51:51.546 xcodebuild[45221:416597] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-06-11 12:51:51.547 xcodebuild[45221:416597] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-06-11 12:51:51.625 xcodebuild[45221:416597] [MT] DVTPlugInExtensionFaulting: Failed to fire fault for extension (null): (null)
2022-06-11 12:51:51.628 xcodebuild[45221:416597] [MT] DVTPlugInExtensionFaulting: Failed to fire fault for extension (null): (null)
** BUILD FAILED **
Xcode's output:
↳
Writing result bundle at path:
/var/folders/l6/zr2yb4p1787b1cbhjdn2ltvr0000gn/T/flutter_tools.tQVcwl/flutter_ios_build_temp_dirmZJ1FK/temporary_xcresult_bundle
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in dependency order
error: failed to read asset tags: The command `(cd /Volumes/Code/Git/svg/ios && /usr/bin/actool --print-asset-tag-combinations --output-format xml1 /Volumes/Code/Git/svg/ios/Runner/Assets.xcassets)` exited with status 72. The command's standard error was:
actool: error: Failed to locate 'actool'.
xcode-select: Failed to locate 'actool', requesting installation of command line developer tools.
(in target 'Runner' from project 'Runner')
Result bundle written to path:
/var/folders/l6/zr2yb4p1787b1cbhjdn2ltvr0000gn/T/flutter_tools.tQVcwl/flutter_ios_build_temp_dirmZJ1FK/temporary_xcresult_bundle
Error (Xcode): failed to read asset tags: The command `(cd /Volumes/Code/Git/svg/ios && /usr/bin/actool --print-asset-tag-combinations --output-format xml1 /Volumes/Code/Git/svg/ios/Runner/Assets.xcassets)` exited with status 72. The command's standard error was:
actool: error: Failed to locate 'actool'.
xcode-select: Failed to locate 'actool', requesting installation of command line developer tools.
Could not build the application for the simulator.
Error launching application on iPhone SE (3rd generation).
Exited
with an alert
The "actool" command requires the command line developer tools. Would
you like to install the tools now?
And if I run it from Xcode it gives me this error:
Showing All Messages
failed to read asset tags: The command `(cd /Volumes/Code/Git/svg/ios && /usr/bin/actool --print-asset-tag-combinations --output-format xml1 /Volumes/Code/Git/svg/ios/Runner/Assets.xcassets)` exited with status 72. The command's standard error was:
actool: error: Failed to locate 'actool'.
xcode-select: Failed to locate 'actool', requesting installation of command line developer tools.
This repetitively occurs even if I press the "Install" button.
Same issue here, but with git instead of actool. Another coworker just also got this but with clang... what is going on over at apple?
What just fixed mine was actually opening up xcode and having it run its installer there instead of allowing the automatic pop-up to continue to "install" and then ask again in a few minutes.
I have created a new project [before pod installed]. I am trying to create documentation using jazzy it's creating fine.
The commend which I used in terminal
jazzy --min-acl internal
Then I installed pod file and trying to use same commend in terminal that time I am getting error like
2021-01-08 12:48:55.363 xcodebuild[1441:132556] [MT] PluginLoading: Required plug-in compatibility UUID B89EAABF-783E-4EBF-80D4-A9EAC69F77F2 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/UncrustifyPlugin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2021-01-08 12:48:55.364 xcodebuild[1441:132556] [MT] PluginLoading: Required plug-in compatibility UUID B89EAABF-783E-4EBF-80D4-A9EAC69F77F2 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Crayons.xcplugin' not present in DVTPlugInCompatibilityUUIDs
Running xcodebuild
Could not successfully run `xcodebuild`.
Please check the build arguments.
Saved `xcodebuild` log file: /var/folders/5t/vxhnv5ys0fb217mwggmpsk6r0000gr/T/xcodebuild-1ECA7C52-5668-4982-A6FD-9D9CDCBAEDBC.log
Failed to generate documentation
/Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/lib/jazzy/executable.rb:36:in `execute_command': /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/bin/sourcekitten ["doc", "--"] (RuntimeError)
2021-01-08 12:48:55.363 xcodebuild[1441:132556] [MT] PluginLoading: Required plug-in compatibility UUID B89EAABF-783E-4EBF-80D4-A9EAC69F77F2 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/UncrustifyPlugin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2021-01-08 12:48:55.364 xcodebuild[1441:132556] [MT] PluginLoading: Required plug-in compatibility UUID B89EAABF-783E-4EBF-80D4-A9EAC69F77F2 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Crayons.xcplugin' not present in DVTPlugInCompatibilityUUIDs
Running xcodebuild
Could not successfully run `xcodebuild`.
Please check the build arguments.
Saved `xcodebuild` log file: /var/folders/5t/vxhnv5ys0fb217mwggmpsk6r0000gr/T/xcodebuild-1ECA7C52-5668-4982-A6FD-9D9CDCBAEDBC.log
Failed to generate documentation
from /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/lib/jazzy/sourcekitten.rb:266:in `run_sourcekitten'
from /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/lib/jazzy/doc_builder.rb:81:in `block in build'
from /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/lib/jazzy/doc_builder.rb:79:in `chdir'
from /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/lib/jazzy/doc_builder.rb:79:in `build'
from /Library/Ruby/Gems/2.3.0/gems/jazzy-0.13.6/bin/jazzy:15:in `<top (required)>'
from /usr/local/bin/jazzy:22:in `load'
from /usr/local/bin/jazzy:22:in `<main>'
jazzy will automatically use Project.xcodeproj instead of using the newly created Project.xcworkspace to build project. This will result in xcodebuild failed at build phase [CP] Check Pods Manifest.lock.
You can use this command to check the build log:
cat /var/folders/5t/vxhnv5ys0fb217mwggmpsk6r0000gr/T/xcodebuild-1ECA7C52-5668-4982-A6FD-9D9CDCBAEDBC.log
The xcodebuild command which jazzy used to build project is
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild CODE_SIGN_IDENTITY= CODE_SIGNING_REQUIRED=NO CODE_SIGNING_ALLOWED=NO
which will select Project.xcodeproj instead of the workspace file
You should use something like this to pass the workspace and scheme to xcodebuild
jazzy --min-acl internal -x -workspace,StackExample.xcworkspace,-scheme,StackExample
Reference:
Issue 111
I am consistently seeing an error when I try to execute bazel run //src:devserver in the angular-bazel-example project.
I am using Windows 10. I haven't been able to find anything that fixes this. I thought the issue might be related to patch or to the path being too long. However, I've used MSYS2 to install patch, I've changed the output directory using the option --output_user_root, and I've tried using a DOS prompt with admin privileges. Nothing seems to help.
The error message
INFO: SHA256 (https://codeload.github.com/golang/tools/zip/3e7aa9e59977626dc60433e9aeadf1bb63d28295) = 2384fa91351a7414b643c5230422ce45f5aa2be8a82727609afd4e64e6973a30
ERROR: Analysis of target '//src:devserver' failed; build aborted: no such package '#org_golang_x_tools//go/gcexportdata': Traceback (most recent call last):
File "C:/temp/vvsv3266/external/bazel_tools/tools/build_defs/repo/http.bzl", line 55
patch(ctx)
File "C:/temp/vvsv3266/external/bazel_tools/tools/build_defs/repo/utils.bzl", line 82, in patch
fail(("Error applying patch %s:\n%s%s...)))
Error applying patch #io_bazel_rules_go//third_party:org_golang_x_tools-gazelle.patch:
java.io.IOException: ERROR: src/main/native/windows/processes-jni.cc(383): CreateProcessW("C:\msys64\usr\bin" -c "patch '-p1' < C:/temp/vvsv3266/external/io_bazel_rules_go/third_party/org_golang_x_tools-gazelle.patch"): Access is denied.
INFO: Elapsed time: 691.367s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (484 packages loaded, 20777 targets configured)
FAILED: Build did NOT complete successfully (484 packages loaded, 20777 targets configured)
Fetching #ngdeps; fetching 245s
Fetching #org_golang_x_tools; Patching repository 15s
Can someone please tell me how to remedy this?
Every time I use git with Xcode, this message appears:
2017-03-31 12:42:40.749 xcodebuild[27773:374610] [MT] DVTPlugInManager: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for KSImageNamed.ideplugin (com.ksuther.KSImageNamed) not present
2017-03-31 12:42:40.943 xcodebuild[27773:374610] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/VVDocumenter-Xcode.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-03-31 12:42:40.945 xcodebuild[27773:374610] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
The KSImage, VVDocument and Alcatraz plugins are from when I installed Xcode 7.3. This is gross and I want to stop the output from appearing. How can I remove these plugins?
I am still seeing this problem with Xcode 9. To resolve the problem, I deleted all my plugins. They stop working starting Xcode 8 anyway.
cd ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/
ls to check your installed plugin and then rm -r <plugin-name> to delete it (them).
In Xcode 13 or macOS 12 it is:
~/Library/Developer/Xcode/Plug-ins/