I have a website with node.js 18.12.1 and gatsby.js v5. Last week, Amplify threw me this error: BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE
My error
My custom build image
I need to especify mi node version.
If i change my build settings to Amazon linux 2 the project does not compile
New custom build image
error to compile
Related
I cannot build my IOS app. the error says
Showing Recent Errors Only
Library not found for -lFBReactNativeSpec
After investigation, i found that the new version react-native "react-native": "^0.64.0" move the react FBReactNativeSpec folder from
../node_modules/react-native/libraries/FBReactNativeSpec"
to
../node_modules/react-native/React/FBReactNativeSpec"
i have checked the build settings header paths, check the react-native pod script file, and the file FBReactNativeSpec is included
the strange thing is that the application is running normally in debug version and not when trying to product/archive for test flight
I got the same problem, when updating an app that had been generated for IOS 13, when updating to IOS 14 the XCode informed that the minimum for the build should be version 12, and it was for 9.0, trying to generate the build in version 9 and 10, these lib not found errors will occur, when accepting the minimum for version 12 the build was generated without errors.
The "library not found" errors occur most of the time because installing the react-native node package and running "pod install" is often not enough.
The error should go away after running a clean build in xcode using the xcworkspace file. After that, running "npm run ios" or "npm start" in the termal should work again.
I recently started my React Native journey and hit a snag before I could even start to code. I followed the guide by Facebook on how to set up your environment for a React Native project, though I installed java SDK, python and node manually instead of through chocolatey. Installing the react native application on my system went smoothly but when I try to run on my Android Emulator by using the command react-native run-android, I run into the following Error message.
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 967 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Launching emulator...
info Successfully launched emulator.
info Installing the app...
The system cannot find the path specified.
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
The system cannot find the path specified.
Note: I have not made any changed in any file nor deleted anything
Steps to reproduce
Run the command react-native init AwesomeProject
cd AwesomeProject
Ensure Emulator is running then start Metro Bundler with react-native start
Run command react-native run-android in a separate terminal to receive error
Steps taken to resolve
I have tried following multiple issues and queries of others with similar problems to no avail
I tried re-installing everything from scratch to no avail, and creating a new project but the same message appears after hours of re-installation
One person suggested running gradle wrapper inside the project folder, but that too made no difference
Another suggested that a file name gradle-wapper.jar would be missing, but its there in the project folder
I tried loading the Android folder of the react native project in my Android Studio, the gradle starts building but there is still no success when the gradle is built
Packages Installed
Node V12.18.2
Java SDK V8
Python 2.7
Android Studio SDK [Android 10.0 (Q)]
Android SDK Build-Tools (Installed)
Android Emulator (Installed)
Android SDK Platform-Tools (Installed)
Intel x86 Emulator Accelerator (HAXM Installer) (Installed)
Please let me know if any further information is required to understand my problem. Thanks!
I want to create the Angular application using Visual Studio 2019 Angular template in Asp.net core but without Node.js as External tool installation. I found that NuGet package manager also providing Node.js and NPM Packages for building Angular app.
So I created the asp.net core projected and selected Angular Template and add NuGet Node.js 5.3.0 that too is saying in readme.txt "Node.js itself is deployed by NuGet, so there is no need to install it locally on dev machines or build servers."
But when I tried to run the angular project then build is failing.
If anyone knows the solution with exact steps so please help me on this.
There is one extra step is required after the Nuget Node.js package installed in the project, which is missing in the node.js document.
Step: Add node.js installed path in PATH Environment Variable (One-time activity per dev system)
e.g: set PATH=%PATH%; C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\NodeJs
or node.js install path can be set manually in the PATH Environment Variable
I have a Docker build running as a task in an Azure devops build pipeline. Recently I had to add a git submodule to the project which contains a .Net Standard 2.0 library which references Entity Framework Core. Now when I run the build I get the following error message:
CSC : error CS8032: An instance of analyzer
Microsoft.EntityFrameworkCore.RawSqlStringInjectionDiagnosticAnalyzer
cannot be created from
/root/.nuget/packages/microsoft.entityframeworkcore.analyzers/2.2.1/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
: Could not load file or assembly 'Microsoft.CodeAnalysis,
Version=2.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
The system cannot find the file specified.. [/.../MyProject.csproj]
I have tried adding the Microsoft.CodeAnalysis nuget package to the project but that just causes more error messages. I have also tried adding Microsoft.Net.Compilers but that can only build under the full .Net framework so doesn't work for other areas of our pipeline.
The build agent being used is Hosted Ubuntu 1604 which should have the most up to date .NEt core SDK. Everything compiles locally.
Found the problem. I was targeting an old .Net version in the dockerfile.
Old command:
FROM microsoft/aspnetcore-build:2.0.0 as build
New command:
FROM microsoft/aspnetcore-build as build
I am trying to upgrade an Asp.net core application on Debian vm. After I copy the new dlls and test with dotnet path-to-my-app.dll I get this error.
LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate registration of tracepoint probes having the same name is not allowed.
Two further clarify, I am upgrading a self contained app. I first stop the running service and then replace the files with new ones and then just do a
dotnet path-to-myapp.dll
and the above error appears. There was no change in appsettings or any other configuration changes. Do I need to stop any other services as well?
For the general public here is the issue and the solution:
The version on my linux VM was 2.1.5 and my App target version was 2.1.0, However the previous target framework version of installed app was 2.1.0 and it was working fine. I only made a few changes and went on to deploy the new version, first it failed to build with the command "dotnet build --runtime linux-x64" complaining about different frameworks to restore and build. So I first changed the project file to use
<TargetLatestRuntimePatch>true</TargetLatestRuntimePatch>
And after that it failed to run with the above error. Finally I changed the RuntimeFrameworkVersion to 2.1.5 to match my host version AND didn't use the "dotnet build --runtime linux-x64" command but Publish instead. I also read about using the Publish command here:
https://codeblog.dotsandbrackets.com/package-downgrade-issue/