Is this a bug when building from command-line with Xcode 8.2?
I'm seeing this when trying to build fbsimctl:
brew tap facebook/fb
brew install fbsimctl --HEAD
==> Installing fbsimctl from facebook/fb
==> Cloning https://github.com/facebook/FBSimulatorControl.git
Updating /Users/lnatan/Library/Caches/Homebrew/fbsimctl--git
==> Checking out branch master
==> ./build.sh fbsimctl build /usr/local/Cellar/fbsimctl/HEAD-244a622
Last 15 lines from /Users/lnatan/Library/Logs/Homebrew/fbsimctl/01.build.sh:
cd /tmp/fbsimctl-20170118-36571-pwc8nx/fbsimctl
/usr/bin/touch -c /tmp/fbsimctl-20170118-36571-pwc8nx/build/Build/Products/Debug/FBSimulatorControlKit.framework
=== BUILD TARGET fbsimctl OF PROJECT fbsimctl WITH CONFIGURATION Debug ≡
Check dependencies
"fbsimctl" isn't code signed but requires entitlements. It is not possible to add entitlements to a binary without signing it.
Code signing is required for product type 'Command-line Tool' in SDK 'macOS 10.12'
** BUILD FAILED **
The following build commands failed:
Check dependencies
(1 failure)
If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/facebook/homebrew-fb/issues
Trying to build manually instead of using the script, I get a similar issue:
=== BUILD TARGET fbsimctl OF PROJECT fbsimctl WITH CONFIGURATION Release ===
Check dependencies
"fbsimctl" isn't code signed but requires entitlements. It is not possible to add entitlements to a binary without signing it.
Code signing is required for product type 'Command-line Tool' in SDK 'macOS 10.12'
** BUILD FAILED **
The following build commands failed:
Check dependencies
(1 failure)
Interestingly, building from Xcode succeeds.
You need to run this with a env variable to disable code signing
export CODE_SIGNING_REQUIRED=NO && brew install fbsimctl --HEAD
It's from installation instructions.
This seems to have been solved in recent fbsimctl releases.
Related
after installing react-native frebase/app it works well for android , but in case of ios ...use of cd ios && pod install ..then pod is not installed ...follow the official documentation Altering CocoaPods to use frameworks
Beginning with firebase-ios-sdk v9+ (react-native-firebase v15+) you must tell CocoaPods to use frameworks.
Open the file ./ios/Podfile and add this line inside your targets:
use_frameworks!
To use Static Frameworks on iOS, you also need to manually enable this for the project with the following global to the top of your /ios/Podfile file:
$RNFirebaseAsStaticFramework = true...
is it same folder ./ios/podfile and /ios/podfile ?
then also not installed the pod and then use of
$RNFirebaseAsStaticFramework = true
use_modular_headers!
at the top of the pod file
and finally pod is installed but when build using npx react-native run-ios and then give a long error
Command CompileSwiftSources failed with a nonzero exit code
2022-07-05 16:47:46.163 xcodebuild[11109:198292] 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-05 16:47:46.163 xcodebuild[11109:198292] 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
** BUILD FAILED **
The following build commands failed:
CompileC /Users/arindam/Library/Developer/Xcode/DerivedData/DemoChat-cttmfseavejzhadnawolzvwrzelz/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsi.build/Objects-normal/x86_64/JSIDynamic.o /Users/arindam/Documents/test_projects/DemoChat/node_modules/react-native/ReactCommon/jsi/jsi/JSIDynamic.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'React-jsi' from project 'Pods')
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler (in target 'YogaKit' from project 'Pods')
(2 failures)
please help i am new to react native...how to solve the issue...
follow this.
xcode command line build failed with com.apple.compilers.llvm.clang.1_0.compiler
if above doesnt work, downgrade firebase version.
ie. package.json
"#react-native-firebase/app": "^12.9.0", // version 12 works great for me, but i get your error when i run version 15.
I have tried the below commands to install dotnet stryker to my project to improve the mutation testing but getting below error message and it does not allow me to install the tool.
Could you please help on this.
Thanks in advance
PS C:\Users> dotnet tool install -g dotnet-stryker
C:\Program Files\dotnet\sdk\6.0.101\NuGet.targets(130,5): error : Unable to load the service index for source https://api.nuget.org/v3/index.json. [C:\Users\AppData\Local\Temp\evv2az1v.kwa\restore.csproj]
C:\Program Files\dotnet\sdk\6.0.101\NuGet.targets(130,5): error : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.nuget.org:443) [C:\Users\AppData\Local\Temp\evv2az1v.kwa\restore.csproj]
C:\Program Files\dotnet\sdk\6.0.101\NuGet.targets(130,5): error : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [C:\Users\AppData\Local\Temp\evv2az1v.kwa\restore.csproj]
The tool package could not be restored.
Tool 'dotnet-stryker' failed to install. This failure may have been caused by:
* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.
Below commands are also getting the same error message
PS C:\Users> dotnet tool install -g dotnet-stryker dotnet tool install --global dotnet-stryker --version 1.0.0
This is most probably not related to Stryker but to some weird NuGet situation. You can check it by installing some common tool, e.g dotnet-reportgenerator-globaltool. I think I have seen this kind of error when setting up local feeds for dev purposes.
So try this:
dotnet nuget list source - list feeds
dotnet nuget remove source <feed_name> - remove everything you don't need or understand
And then try installing Stryker once again.
While trying to build a simple Kogito application with the Persistence profile enabled the build failed complaining that the lib stdc++ was not found:
/usr/bin/ld: cannot find -lstdc++
The builder image is based on the ubi8-minimal and to build it the s2i tool was used with the following command was used:
s2i build https://github.com/kiegroup/kogito-examples --context-dir jbpm-quarkus-example quay.io/kiegroup/kogito-quarkus-ubi8-s2i:0.8.0-rc1 kogitotest:10.0 --runtime-image quay.io/kiegroup/kogito-quarkus-ubi8:0.8.0-rc1 --loglevel 5 --env MAVEN_MIRROR_URL=http://nexus.apps.spolti.cloud/nexus/content/groups/public/ --env NATIVE=true --env MAVEN_ARGS_APPEND="-Ppersistence"
As first hint I think it could be something related with the libstdc++-static because when running the same build on my local machine it works and the only difference I found around this the stdc++ lib was that my machine have the llibstdc++-devel and static packages while the image only have the libstdc++, tried the to install the devel one, but no luck thus I thought it could be something related with the static one.
The fix:
To solve this I had to symlink /usr/lib64/libstdc++.so.6.0.25 to /usr/lib64/libstdc++.so
but not sure why on my machine it works without the symlink and have piratically the same libs available, eg libstdc++.so.6.0.27 with a symlink to libstdc++.so.6
Proper fix:
Just install gcc-c++ package.
I install sorbet according to their instructions on the GitHub README:
Install the dependencies
brew install bazel autoconf coreutils parallel Clone this repository
git clone https://github.com/sorbet/sorbet.git cd sorbet Build Sorbet
bazel build //main:sorbet --config=dbg
But when I run it, I got the following:
$ bazel-bin/main/sorbet -e "42 + 2"
👋 Hey there! Heads up that this is not a release build of sorbet.
Release builds are faster and more well-supported by the Sorbet team.
Check out the README to learn how to build Sorbet in release mode.
To forcibly silence this error, either pass --silence-dev-message,
or set SORBET_SILENCE_DEV_MESSAGE=1 in your shell environment.
No errors! Great job.
I want to install the release build because I want to use a well supported sorbet so I go to their GitHub README again and see this:
--config=release-mac and --config=release-linux Exact release configuration that we ship to our users.
So I run this:
bazel build //main:sorbet --config=dbg --config=release-mac
But it end up with this line:
FAILED: Build did NOT complete successfully
I tried this too:
bazel build //main:sorbet --config=release-mac
But it end up with this line too:
FAILED: Build did NOT complete successfully
What should I do to install a release build of Sorbet?
Readme file in Sorbet repo describes how to compile Sorbet, not how to install an existing release.
To install existing release, follow guide at https://sorbet.org/docs/adopting
If you insist on compiling release from sources on your own, in order to help you, we'll need more build log, as you didn't include messages that told what specifically went wrong.
Now, using a crystall ball, I would guess that you're attempting to compile Sorbet on OS X Mojave that doesn't ship with system C++ headers and thus build fails to find math.h or stdio.h. Sorbet Readme contains instructions for how to install headers in the Readme: https://github.com/sorbet/sorbet#common-compilation-errors.
I'm testing React Native 0.56.0-rc.2 on Mac OS Mojave and Xcode 10.
Running:
react-native init TestProject --version="0.56.0-rc.2"
cd TestProject
npm run start
react-native run-ios
Which generated some long errors.
Entering Xcode gave me a failure on missing config.h for glog, which I found could be built manually:
cd ./node_modules/react-native/third-party/glog-0.3.4
./configure && make && make install
Which passed that stage, but got me on yet another issue
(...)/node_modules/react-native/third-party/glog-0.3.4/src/glog/logging.h:85:10:
'gflags/gflags.h' file not found
I can't find anything related to RN and this on Google or Stack Overflow, only references to other packages and instructions to install those on a Debian-based system.
Is this a known issue?
Running this from the project directory fixed it for me:
cd ./node_modules/react-native/third-party/glog-0.3.4 && ../../scripts/ios-configure-glog.sh
This manually triggers the config script
A simple and quick resolution.
In Xcode, go to File->Project/Workspace settings.
Change the build system to Legacy Build system.
This is the resolution from Wesley's link. Saw something the other day about posting the direct answer and trying to avoid linking because links / websites can change. I was going to leave this as a comment, but don't have enough rep.
Update
It is a known issue, tracked here:
https://github.com/facebook/react-native/issues/19774
I resolved it by running following steps
In the root of the project, run npm install or yarn - install packages
cd node_modules/react-native - go to node modules directory
scripts/ios-install-third-party.sh - install # node_modules/react-native/third-party
cd third-party - go to newly created third party directory
cd glog-0.3.x - ls -la to find your directory version number or just use tab to auto-complete)
./configure - run setup
cd ../../../../ - change back to your project directory
react-native run-ios or react-native run-android - deploy
If any of these solution does not work, please check your project path. Project path and/or directory names should not contain any
space in its name or you can create project on Desktop or in Documents
directory.
Because of invalid name in project path, React Native project unable to link / add glob header files inside project / workspace.