I got the following error after runing a npm start command with a running application in other pcs with no trouble, I have tried cleaning the cache, deleting the package-lock.json file and node_modules folder to recompile, but always get the same error?
Any ideas?
Here'r the complete Error message.
Failed to compile
./src/pages/artistas/Barrios.js
Module not found: Can't resolve '../../assets/img/recibos/Álvaro-Barrios---Alegría-de-la-paz.jpg' in 'C:\Users\Stefany\Downloads\sanaciones-master\sanaciones-master\src\pages\artistas'
This error occurred during the build time and cannot be dismissed.
--
It is interesting that it seems to work for some miliseconds but then it fails and the error message appears. The paths to the image is correct, since as I mentioned it works perfect in other pcs.
Thanks in advance for your help.
Related
after running react-native run-windows, it brought this error....
5>midlrt : error MIDL1001: [msg]cannot open input file [context]Error opening or processing WinMD c:\users\hp\desktop\coding\react-native\desktop app\dhymm\windows\packages\microsoft.ui.xaml.2.3.191129002\lib\uap10.0\microsoft.ui.xaml.winmd. HRESULT 0x80070003. [C:\Users\HP\Desktop\CODING\REACTNATIVE\DESKTOPAPP\dhymm\node_modules\react-native-windows\Microsoft.ReactNative\Microsoft.ReactNative.vcxproj]. Check your build configuration.
See C:\Users\HP\AppData\Local\Temp\msbuild_11100.err
any help would be appreciated
i have also configured my paths to only letters, ran npm i again, tried npx react-native run-windows it brought the same error
when i run ng serve on node js command prompt i got this error "The serve command requires to be run in an Angular project, but a project definition could not be found". and after i run this command tong update #angular/cli --migrate-only --from=11.2.10 got also this error An unhandled exception occurred: Could not find package.json
See "C:\Users\User\AppData\Local\Temp\ng-Lbnxei\angular-errors.log" for further details.
can any one help me
Try like this
ng update #angular/cli --from 10 --to 11 --migrate-only
This is wrong syntax --from=11.2.10
After I installed the react-icons package, my code threw an error saying my babel-loader was missing, so I installed that package too.
Next thing I knew, I ran yarn start and this error came up:
Assertion failed: (napi_create_string_utf8(env, events->events[idx].path, NAPI_AUTO_LENGTH, &args[0]) == napi_ok), function fse_dispatch_event, file ../src/fsevents.c, line 147.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I tried using npm start and the app started just fine.
What's wrong?
I believe this is caused by an upstream issue with fsevents.
The App is working fine, in fact I have built 2 release APKs. This time I modified the code and came to do ./gradlew assembleRelease and I got the following error:
Error
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
Expectation
To generate a healthy APK ready to publish.
Extra Info
I have done the signing and the .keystore in the right place ../android/app
Updated ../android/gradle.properties as instructed
Here is the complete stacktrace:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:mergeReleaseResources'.Close stacktrace
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:110)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ResolveBuildCacheKeyExecuter.execute(ResolveBuildCacheKeyExecuter.java:79)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)
at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Screenshot from the Scan1
Screenshot from the Scan2
Screenshot from the Scan3
from android Studio - I believe it is related to the issue
Screenshot from the Scan4
I believe this could be a duplicate of this question:
Error Execution failed for task ':app:mergeReleaseResources' building APK
The problem occured becaused when I tried to build once, it has
created drawables dirs on android/app/src/main/res/. Then when I tried
on second time, it has shown me this error Execution failed for task
':app:mergeReleaseResources' building APK
I just deleted the drawable-* dirs and it worked.
To remove the directory drawable--*:
rm -rf android/app/src/main/res/drawable-*
There is no drawable folder inside res, still the error occurs.
While running the emulator the build is successful and emulator works fine but I couldn't take release apk because of build failure.
I am getting following error while running a build definition.
I tried to give read/write permission by right clicking the Builds directory, but after running the build using build definition the permissions get reset.
The files get created by calling "gulp" command from a post script bat file.
How to get rid of this error?
I was wondering if it's related to the npm install issue. Please refer this npm install fails on Windows with "EPERM, operation not permitted" for more details.
Here is also a similar question Visual Studio 2015 hybrid app - getting "EPERM, operation not permitted"