EXPO EAS BUILD "HTTP Error: Response code 400 (Bad Request)" - javascript

I'm trying to build an apk to test my app but every time I run eas build i get the same error. I've already searched everywhere and can't find a solution.

Running:
expo update
solved this problem for me and I was able to successfully run eas build again. I believe there were incompatible packages installed that needed to be updated.

I found the problem, it looks like my ISP was blocking the requisition, using VPN solved the problem

Related

Error pushing React app to Heroku - "remote rejected main-> main (pre-reseive hook declined)"

I'm gettig this very frustrating erro while trying to push my React app to Heroku. I was able to push it up with no problem in the application's earlier development, but for some reason it now gives me the same error message all the time:
! [remote rejected] main -> main (pre-receive hook declined) error: failed to push some refs to 'https://git.heroku.com/sapient-origin-alpha.git'
The only thing I can think of is that there is some issue with the version of react I'm using (I tried react 18 and 17, both gave the same results). But again, I was able to push it up before with no problem so I'm not sure. My other thought was that it's the client-side package.json since it's saying the build is failing.
Another thing worth mentioning is that I re-named the Heroku app, but afterwards I removed my local git remote and created a new git remote with the updated Heroku app name. So maybe this had something to do with it? This is basically what I did:
*rename heroku app*
$ git remote rm heroku
$ heroku git:remote -a sapient-origin-alpha
If anyone is able to help me on this I would very greatly appreciate it.
Nevermind I'm just dumb. It literally told me what was wrong in the error message slightly above the text in the image I provided.
The problem was in the client-side package.json because of some dependency I was using. Make sure to double check your package.json file for things that could be causing a similar error, and delete your package-lock.json then run npm i again to refresh the file.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'

I am developing a mobile app with using react-native on WebStorm and trying to test it via an Android emulator(Pixel API 28) which I created via using AVD Manager of Android Studio. The problem is when I run the react-native run-android command, I get the following error:
Could not determine the dependencies of task ':app:preDebugBuild'.
> Could not resolve all task dependencies for configuration
':app:debugRuntimeClasspath'.
> Could not resolve com.facebook.react:react-native:+.
Required by:
project :app
> Failed to list versions for com.facebook.react:react-native.
> Unable to load Maven meta-data from
https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml.
> Could not HEAD
'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'.
> Connect to jcenter.bintray.com:443 [jcenter.bintray.com/35.158.228.205, jcenter.bintray.com/3.120.47.203] failed: Read timed out
I tried to clean up the cache with using the command below but it did not worked:
npm cache clean --force
I could not find some similar problems on the web and I am not sure what to show related with this problem.
When I try to run one of my previous project which was perfectly running, after getting this error and I saw that it also throws the same error. Similarly, when I create a new react-native project and try to run it, then I also got the same error. How can I solve this?
I am still loking for a solution. Anyone knows how to solve it?
I finally figured out the problem. I was connecting to internet via my school's network and it was restricting some downloads. So, that is why I got this error. For the ones who encountered with the same error, try to connect to the link in the error to if it is forbidden or not.

React-Native (CRNA) Packager stops running

I'm working on a react native app built with CRNA.
Everything was working fine until yesterday. Everytime I run the packager with
npm start I get this:
Error starting packager: Error: Could not access packager status at http://localhost:19001/status. Are you sure the packager is running and reachable?
at Timeout._onTimeout (C:\xdl#50.8.0\src\Project.js:1350:11)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5)
While running the packager I tried to reach the address through my browser and it seems to work for a while (it says the packager is currently running), but suddenly stops working and the packager throws me the error above.
I tried to run npm install and checked my package.json but I can't find anything helpful to solve it.
I also tried with a different network, same error.
Could it be a typo in my code that makes the packager go crazy or I have to check something else?
There is an open bug on expo-cli GitHub. I believe need to wait until the bug is resolved.
I am too facing the same issue and for a moment I am using Snack Expo to work on the same machine as of now.
Hope this helps!

proxy error econnrefused grunt

I have ran into a problem when running through grunt.
I get a proxy error: Econnrefused when running grunt serve.
I ran --verbose too and it looks like the request is getting blocked. I think it could be related to my organisations network setup but don't know this for sure.
The web page loads but has no data etc in.
grunt serve --verbose output
can anyone help please?
thanks,
Figured out what this was....the second server wasn't starting correctly so the proxy had nothing to connect to. Running maven was the cause of the issues.

Meteor js Windows install error "Failed to contact install server"

I have tried running the install with "Run as Admin" feature on windows too, but the same issue persists.
I see this question has been posted before but still no resolution given.
Basically the following error message comes in the middle of the install and the install stops. Please help.
Error message:
"Failed to contact install server. Please try again later."
Check if you have Node js already installed before installing meteorjs other wise it crashes on Windows sometimes hope it helped.
https://nodejs.org/en/download/
Install meteor with this installer: https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows
If you are behind a proxy set these parameters HTTP_PROXY and HTTPS_PROXY: Using Meteor behind a proxy
Update your meteor installation: meteor update
The meteor will be updated to the last version.
install from https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows (the >60MB file) and set the user.meteor folder in your path
the problem with windows installation is too long pathnames (>256) so better try a linux VM

Categories