PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/viniciusachterberg/Library/Developer/Xcode/DerivedData/AgrinessPresence - reactjs

I'm on a big problem in my actual project. Everytime when I try to run iOS simulator this error appear in my log. I tried chance Xcode version, delete all pods, change zshrc file, but nothing happens.
Anyone to help? If I create a new project and run npx react-native run-ios works to me but on this specific project dont run anything.
Infos:
RN Version: 0.64.0
oS infos: Macbook Air M1 big Surr
Node version: v14.0
Follow the error:
objc[24913]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1edc1bbc8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x118130318). One of the two will be used. Which one is undefined.
** BUILD FAILED **
The following build commands failed:
PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/viniciusachterberg/Library/Developer/Xcode/DerivedData/AgrinessPresence-aatyymmaxydmoqfhtgtytzoqepin/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-48ABC94909B35DCD398CB750635A0D8D.sh
(1 failure)```

Related

my React app does not update during runtime, when I make changes and save. BUT works on my Macbook but not on my Windows PC

On Windows device:
When I run react-scripts start
In my terminal it says that my "webpack compiled successfully".
When I apply new changes to my code and save, the app does not update on runtime with the new changes.
On Windows Device
I have tried this in both powershell and a wsl (ubuntu 18.04) terminal with node v16.19.1
When I run react-scripts start my react-app is compiled successfully
But when I implement changes it does not update directly.
When I terminate the terminal and rerun the script
I can see my change, but again does not update on runtime again.
(No Result) I have removed my node_modules and redid all my dependencies.
(No Result) I have started with ubuntu 22.02 and downgraded to 18.04
(No Result) I have downgraded node 18 to 16 too
project is written in .jsx
On my Macbook and expected result
When I run react-scripts start my react-app is compiled successfully
and when I make changes and save, it does update on runtime.
Question
I would like to know why my react-app does not work on runtime on my Windows device and a possible solution.

Ionic build failed without specific error

After cloning my Ionic React project to my server, I ran npm install and all dependencies were installed as expected.
But when I tried to build my app running sudo ionic build --verbose, it tooks much more time than usual and ended like this :
eslint:lint-result-cache Persisting cached results: /var/www/html/ms-users-front/node_modules/.cache/.eslintcache +0ms
eslint:cli-engine Linting complete in: 4827ms +48ms
//It stay here for at least 10min before to failed while it tooks 1min in my local machine.
The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
[ERROR] An error occurred while running subprocess react-scripts.
react-scripts build exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
ionic:utils-process onBeforeExit handler: 'process.exit' received +0ms
ionic:utils-process onBeforeExit handler: running 1 functions +1ms
ionic:utils-process processExit: exiting (exit code: 1) +44ms
My server is an ec2 instance with httpd installed and everything was working great before I tried to build a new version yesterday.
With exactly the same process, the app is building perfectly on my local machine...
I tried npm update, delete eslint cache, and build but without success.
I tried to downgrade Typescript to 4.1 because I had a warning saying that Typescript should be >4.5 and it was 4.7. But after some tests on local, it looks like this has no incidence on the build process.
I'm totally stuck and I absolutly don't know what to try.

React Native: XCode: Build failed with error "EMFILE: too many open files, watch"

– MackBook Air M1
– macOS 11.3
– XCode 12.5
– react native 0.64.1
– node 16.0.0
– npm 7.15.1
– watchman 2021.05.31.00
When I try to archive a project or build one for a device, Xcode stops building with an error:
/Users/aptyp/Projects/Proffmylife/Client/node_modules/metro-hermes-compiler/src/emhermesc.js:81
throw ex;
^
Error: EMFILE: too many open files, watch
at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:204:21)
Emitted 'error' event on NodeWatcher instance at:
at NodeWatcher.checkedEmitError (/Users/aptyp/Projects/Proffmylife/Client/node_modules/sane/src/node_watcher.js:143:12)
at FSWatcher.emit (node:events:365:28)
at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:210:12) {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
filename: null
}
Command PhaseScriptExecution failed with a nonzero exit code
But for the simulator, the build works fine.
I have tried to reinstall node_modules, Pods, watchman with brew. Also I've created files limit.maxfiles.plist, limit.maxproc.plist into dir /Library/LaunchDaemons/ and now ulimit -a shows processes 2000 and file descriptors 524288. Restarting computer and unlock Keychain.
On my PC with Hackintosh I don't have this problem.
This error is because of a bug in module fsevents for mac m1 silicon. See the thread: https://github.com/facebook/metro/issues/668
It got fixed with new version of watchman. Upgrade your watchman through brew. Delete your project and download from git and rebuild everything along with pod install and then it should archive no problem.
Facebook guy admitting to the bug and fixing it
I created a new project with the same name, installed all the latest packages and copied the code. Only after that the project was built success.

Play Application Couldn't be Started

Recently I've been assigned for a project created with AngularJs and it uses Java Play framework to run it. I use IntelliJ-Idea IDE for the development and to run this application.
Once I clicked on "Run", it gives me following errors in the console.
'force' enabled
Will run: [gulp, --gulpfile=gulpfile.js, watch, --force] in /home/supuns/Projects/bd-business-portal/ui
java.io.IOException: Cannot run program "gulp" (in directory "/home/supuns/Projects/bd-business-portal/ui"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:248)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
[trace] Stack trace suppressed: run 'last compile:run' for the full output.
[error] (compile:run) java.io.IOException: Cannot run program "gulp" (in directory "/home/supuns/Projects/bd-business-portal/ui"): error=2, No such file or directory
[error] Total time: 2 s, completed Oct 24, 2016 10:54:25 AM
Process finished with exit code 1
I can't figure out what is happening because I'm new to the environment.
UPDATE:
Sorry about the less information I have given in my question. I have globally installed gulp but still it is not working.
Here's the content of build.sbt file.
name := """bd-business-portal"""
version := "1.0-SNAPSHOT"
lazy val root = (project in file(".")).enablePlugins(PlayJava)
scalaVersion := "2.11.7"
libraryDependencies ++= Seq(
javaJdbc,
cache,
javaWs
)
With the help of my team members I have found the reason that cause this issue is IntelliJ-Idea doesn't know the path to 'Gulp'. I'm using Ubuntu 16.04 and even though I have set the path globally it doesn't understand where to find gulp.
Therefore I have installed sbt and from the IntelliJ terminal ran the command:
sbt run
and it worked.
Update
As I had to work on multiple Play framework sbt projects, doing "sbt run" on the terminal and closing IntelliJ windows to free the port was bit hectic. Therefore I decided to find the actual path variable that created this behavior and I found the PATH variable saved in /etc/environment was "/home/supuns/.nvm/versions/node/v6.9.1/bin/gulp" and I changed it to
/home/supuns/.nvm/versions/node/v6.9.1/bin
Then the IntelliJ "Play" button worked as intended.
I also faced the same issue. I fixed it by installing gulp cli along with gulp. Below 2 commands fixed my problem:
npm install -global gulp-cli
npm install gulp --save-dev

BlackBerry 10 Cascades - Running app on the simulator

I am new to blackberry development and ran into this problem several times and cannot find a solution.
When I try to run an empty cascades project just with a simple HelloWorld label I get the following error
Deployment Failed: Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: Debug native: on
Info: File size: 190910
Info: Installing com.example.HelloWorld.testDev__HelloWorld7d1bfe91...
Info: Processing 190910 bytes
I'm using Momentics, VMware running BB10 Dev Alpha Sim and followed all the instructions here. http://developer.blackberry.com/cascades/documentation/getting_started/setting_up.html
I made sure my build config is set to Simulator-Debug and not even the example projects are able to run on the simulator.
Edit: I am not sure if this bit of info helps but when I try to run the application, the Progress hangs at 91% before the error dialog appears.
May be you are not setting the development Mode (like current Development Mode Simulator or Device) . I also getting the issue that Project Compile but not able to run on virtual Machine , today I sort the issue . check out the link http://supportforums.blackberry.com/t5/Native-Development/BB10-Native-Cascades-SDK-not-connecting-to-Alpha-BB10-simulator/td-p/1719865/page/5

Resources