The server has encountered a temporary p‌r‌o‌b‌l‌e‌m while setting the default version. Please try again later - google-cloud-endpoints

I am getting this weird error while setting up my cloud backend
when i deployed my app, the url Http://"app-id".appspot.com
is landing on this page
but the url http://1-dot-"app-id".appspot.com is lannding on the right page
everything else works and its not a welcome-file issue.
then in the developer console i tried to set the default version and it gives me a error.
They say its a temporary problem but i have tried this for 2 days...
Any suggestions ?

Found the solution after 3 days of googling and digging in settings.
This also works if your app engine project dosent have a default bucket.
go to the old developer console https://appengine.google.com/
goto main > versions and set the default version here.
the newer console didn't work for me !
Also,
goto application settings
scroll down completely till you see the title "Cloud intigration"
it reads: "Create a Google Cloud project as well as a Google Cloud Storage bucket and a new style service account for this application"
click create.
This option is not there in the newer console.

Related

I'm having a problem with firebase when i deploy my project

I made an application and finished it, and wanted to upload it to firebase. When I type in the terminal "firebase deploy", everything appears fine, then the link to the site appears in the terminal normally.
But when I click on it to open the site, a message appears saying:
Firebase Hosting Setup Complete
You're seeing this because you've successfully setup Firebase Hosting. Now it's time to go build something extraordinary!
As you can see in the attached picture!
Make sure that index.html inside build folder and the one outside the build folder must be the same.
If they are same then try reloading after some time. When I was having the same issue it worked without doing anything and reloading after sometime (in my case around 10-15 minutes)
Here is a github issue that has detailed discussion on this.
https://github.com/coreui/coreui-react/issues/55

Firebase: Still old version after deploy to hosting, how?

I have received for maintenance a rather primitive react app hosted on firebase (developed by someone else). Now weird things are happening:
I change content of a file (even simple text change)
Run deploy (hosting) - I see in firebase console that deploy was successful
Still: page content is still old, without changes!
How can it be? I use Chrome incognito mode to ensure no cache on browser side, and Firebase docs say that deployment clear server cache.
Turns out it is about cache setttings of firebase. I've seen people wrote default it is about one hour (sic!) so I overridden the cache header settings as referenced and now it is immediately visible after publishing.
https://firebase.google.com/docs/hosting/manage-cache

Publish editor add-on to G Suite Marketplace as internal (domain only) app for G suite

I developed a Google Form add-on and tried to publish it in the G Suite Marketplace as private (only for my G Suite domain) by following this guide.
I did this more than 2 days ago and the add-on is still not visible in the G Suite Marketplace, but the guide says:
If you selected Private visibility for the add-on, the add-on should become available for use after a few minutes.
So I think there is some issue here.
Earlier in October, the guide was different as the publication in Chrome web store was also required. The new guide has no more steps to publish to this Chrome Web Store so I did not do this.
Here are some ideas of the root cause of my issue (the fact that it's not visible in G Suite Marketplace):
Chrome web store is still required (but the guide says it's no more required). I have some doubt as this guide has been changed a couple of weeks ago.
In G Suite Marketplace SDK, the "publish" tab is may be also required? But the guide explains only the "Configuration" tab. Is this "publish" tab now required?
The guide is wrong?
I need to wait more time?
My guess is that the root cause is number 2. I guess the "publish" tab is required but the guide does not require this
Edit
When I was typing this issue here, the user guide was updated. Now I see that it's again required to publish the app to the Chrome Web Store, this has just been added : "Step 5: Configure the Chrome Web Store listing and publish".
It seems the user guide has been updated again, there is no more step 5.
I manage to get my private add-on available as a domain app after "forcing" the configuration page to save new settings. Here is how.
After the migration, the configuration page was set up but the publish page only show this message
Please setup 'Configuration' tab before publishing.
But on the configuration page, the save button was disabled as all the fields have been imported from CWS.
To enable the save button, I only had to change the privacy policy URL with a new one and save.
After that, the publish page showed the classic settings and I was able to publish the add-on. It appears on the GSuite Marketplace Domain App a few minutes after that.
I hope it helps.
In addition, but you may have done it already, the project is attached to my organization in GCP and it is marked as internal-only

Cannot download google-services.json from firebase console

I'm trying to download google-services.json from firebase console. The error is There was an error. The config file cannot be downloaded at this time. as it can be seen in the below screenshot.
There are answers on Stackoverflow which didn't work for me (one and two). Specifically, clearing cache and history, using a newly installed chrome, trying with firefox and edge, using incognito tabs, didn't work.
What else can be done to get rid of this annoying error?
For me also I had this issue. Before trying anything, I refreshed/reloaded my page, and it works. After refreshing my page, I was able to download google-services.json file.
I had the same problem for a while with firebase google
what I did was to open the Developer Options for the web and looked at the request response from google
and I found out that the network response is very clear:
"The Google cloud platform for this project is disabled please go to https://console.cloud.google.com/apis/api/firebase.googleapis.com/overview?project=<YOUR_PROJECT> and enable"
but for some reason the UI is very un-clear
Very simple solution, go to the link below and enable your project:
https://console.cloud.google.com/apis/api/firebase.googleapis.com/overview?project=
While in my case, the issue was caused by my ad blocker. I opened network monitor through developer tools and found out that my ad blocker was canceling post requests sent by Firebase. Disabling it for Firebase solved my issue.
I was using Brave , stopped ad blocker but still it does not work , Use Chrome if nothing works ....it worked for me..

Firebase Hosting not updating connected domain

I'm hosting a web app with Firebase hosting service.
I build my app and then deploy it using firebase command tools.
The build is successful and the firebase domain shows the update:
https://calmeet-a7271.firebaseapp.com/e/-KsC5suhESWNwzYw6rtq
But the connected domain doesn't show the update:
https://calmeet.co
You can see the difference in these two links by the Settings (cog) button on the top right. https://calmeet-a7271.firebaseapp.com/e/-KsC5suhESWNwzYw6rtq has the settings button while https://calmeet.co does not
I'm not sure what I'm doing wrong, I thought this would be automatic.
DNS seem to be working alright. I don't see any error in firebase
I had this same issue. It was caused by doing back to back ng-build and firebase deploy commands in the terminal.
Turns out chrome was caching my connected site. If I opened it in a different browser (safari) it would update. Another way to fix it in chrome is to clear recent browsing data by going to your browser toolbar, clicking More and then More Tools and then Clear Browsing Data.
Short answer, Clear caching browse and try again or open another browser.
Hope this help.
Just do a hard refresh (cmd + shift + r) on your website on Chrome. That worked for me.

Resources