Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 6 years ago.
Improve this question
Unable to deploy to GAE (java) today. I was able to deploy until yesterday evening. Anyone else has the same problem? how did you solve?
09-Mar-2016 11:15:04
java.lang.RuntimeException: Bad authentication response: 404 Not Found
09-Mar-2016 11:15:04
Unable to update app: Bad authentication response: 404 Not Found
thanks
I was having this same issue. As it turns out the authentication method (ClientLogin) I was using to deploy to appengine was deprecated (I was deploying using mvn gae:deploy). Google now wants us to use their new OAuth 2.0 authentication for deploying to appengine: https://cloud.google.com/appengine/docs/deprecations/clientlogin
To fix this issue I had to update my appengine maven plugin to use the latest version so I could deploy.
I added this to my pom.xml:
<plugin>
<groupId>com.google.appengine</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>1.9.34</version>
</plugin>
Then I used this command to deploy (instead of mvn gae:deploy):
mvn appengine:update
For more info you can check out this info on how to deploy to appengine: https://cloud.google.com/appengine/docs/java/gettingstarted/uploading
I had opened multiple google accounts. So, I did close all and deployed it again. It did deploy. It was my mistake.
Install Google Plugin for Eclipse.
Open your project in eclipse. Once you install the plugin successed, you will see a new button of "G" on eclipse buttons bar.
Click the "G" button and then click "Deploy to App Engine".
Done.
Related
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 1 year ago.
Improve this question
I'm new to react and started learning it recently. Last day I created my 1st app and I was able to see it in the localhost:3000 before taking a break I bookmarked the page and shut down my pc.
Now when I try to access localhost:3000 it show me that it cannot connect. So I tried to use the "npm start" command in visual studio code terminal. But I received several errors and still trying to figure out how to start again the development server.
Any idea how to fix it?
I solved the problem. The fact is that react created inside the project a folder called js inside it there is a package.json that has this small code
{
"dependencies": {
"tar": "^6.1.11"
}
}
when i restarted the visual studio my location in terminal was inside the js folder so when I was trying to run the npm start command it wasn't working.
The fact is that react creates also another folder called my-app inside this one there is another package.json file. So in my case the solution was to move inside the my-app folder using cd. Attention the - symbol how spaces cannot be freely used inside the terminal. So the right way to navigate inside was
cd 'my-app'
if you don't use the quotes it will throw an error. now that I was inside the real app folder I was able to start the server using
npm start
This is a little bit strange and react devs need to add this fact in the documentation. Considering it automatically creates 2 folders and 2 package.json files making it confusing for newbie people like me
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
I just updated to Xcode 12 and now my react native project (which was working just before updating) will not run and outputs this error
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
info Launching "app.lfgo.release"
error Failed to launch the app on simulator, An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=4):
The request to open "app.lfgo.release" failed.
Underlying error (domain=FBSOpenApplicationErrorDomain, code=4):
The operation couldn’t be completed. Application info provider (FBSApplicationLibrary) returned nil for "app.lfgo.release"
Application info provider (FBSApplicationLibrary) returned nil for "app.lfgo.release"
The same was happening to me when upgraded to Xcode 12. What helped was to (if using lock files) install #react-native-community/cli-platform-ios as devDep and bump version in all #react-native-community/cli-platform-ios entries in yarn.lock file to 4.13.0
Not sure why this fixed it for me or anything about it but...
Using npx react-native run-ios throws this error for me, but when i built through xcode it worked fine. Makes no sense to me but oh well...
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
I've tried reinstalling node and removing appdata/roaming/npm and npm-cache. I've created several apps before so i'm not sure what's going on. Any help is appreciated.
this issue is fixed with 2.2.2 version of is-promise package. If you still experience problems creating new CRA, consider npm install -g --force create-react-app
If even then bug is still present, please comment your issue to this github issue
I would:
Restart the machine. Ensure you log out of your session if needed
Re-install Create React App
Uninstall yarn and reinstall
Reinstall node, ensure you use a newer version
Use a different network connection, maybe something is being blocked by a firewall
I would: change my node version.
Refer the following link
I read up on all the comments saying that this seems to be a recurring problem, and perhaps a temporary one. I looked at Bloodshot the movie and came back, tried again and it now works. Only thing i changed was trying it in a different folder (which i did multiple times before). Perhaps it was Vin diesel doing some magic or there was some problem with npm. Not sure but it works now and im thankful for it, and all the responses.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I've been a long time user of appcfg.py and I even build some bash scripts on top of it.
Should we switch to gcloud app deploy? Will appcfg.py be deprecated? If yes what is the timeline?
Why isn't there a grace period for backward compatibility of the yaml file? Switching to gcloud app deploy I get:
The [application] field is specified in file [.../app.yaml]. This
field is not used by gcloud and must be removed. Project name should
instead be specified either by gcloud config set project MY_PROJECT
or by setting the --project flag on individual command executions.
and
ERROR: The [version] field is specified in file [.../app.yaml]. This
field is not used by gcloud and must be removed. Versions are
generated automatically by default but can also be manually specified
by setting the --version flag on individual command executions.
I am saying this as this was possible w/ the module/service field:
WARNING: The "module" parameter in application .yaml files is
deprecated. Please use the "service" parameter instead.
How do you upload queue.yaml, dispatch.yaml and cron.yaml with gcloud app deploy?
What are the differences between the 2 ways of deploying an app?
I'm interested in caveats & things to watch for like:
FLAGS --promote Promote the deployed version to receive all traffic. True by default.
That means w/ gcloud app deploy the app will be deployed and the new version will be set as the active one... this is exactly the reverse way appcfg.py did things as there you would have to call set_default_version to mark a version as active.
This raises my last question: if I opt to NOT make it active by using either
$ gcloud config set app/promote_by_default false
or
Use --no-promote to disable.
will I have to redeploy w/ default value so I can make it active?
Long story short:
gcloud app deploy is going to be the preferred path for deployments going forward, and is currently supported. You'll have about a year after we declare deprecation to transition.
Before we deprecate appcfg.py, we'll have a full migration guide with all of the changes. We don't want full backwards compatibility, because we're seizing this chance to fix some warts with the old tooling.
You can run gcloud app deploy cron.yaml and so on to deploy the alternate YAML files.
Again, we're planning on writing a migration guide before we want to force you over to the new tooling.
So I think you can punt on this until we've officially deprecated the appcfg tooling–gcloud app is really meant for brave explorers who want the newest and shiniest for now.
Folks,
I'm using the recently released Google Cloud SDK 0.9.56 on Windows 7x64.
When trying to gcloud deploy my app using web.xml and appengine-web.xml, I get a response:
ERROR: Found no valid App Engine configuration files in directory
When trying to do the same with apps defined with app.yaml there were no issues.
Teammates with older SDK versions don't seem to have an issue.
Is there a mandatory requirement to use app.yaml in all apps?
P.S: This question might be related but its actually a different issue.
sorry about this.
That question you linked is actually the same issue. You can use the new maven plugin described there to translate your appengine-web.xml to app.yaml automatically. We have a gradle plugin coming out very soon to do the same thing.
If you'd like to keep using gcloud directly without Maven or Gradle, you'll need to translate the appengine-web.xml to an app.yaml for now.
Let me know if I can help.