Cannot delete project - nest-device-access

I am unable to delete a project from the Nest Device Access Console. When I click the delete icon and click delete, it processes and comes back with a pop-up that says "Could not delete project" with no other information. If I try to delete the OAuth Client ID, it processes and comes back with a pop-up that says "Could not update project data" with no other info.
Any advise would be helpful.

Resolved: this seemed to be just a temporary issue with the website.

Related

Can I use HTTP request and receive response with Excel add-in?

I have a download button and it will save excel file where user selects.
And it's working correctly.
Now I want to check if there is already file exists where user saved last time when user clicks button again.
I think this is related with Web API or OS file managing system.
What I want is like this:
If file exits, just update it, not show save-as dialog again.
But if user deleted or renamed, it will shows save-as dialog again.
Please help me how can I handle this.

How do I delete a database from Firebase?

This must be staring me in the face, but don't see the command. How do I delete an unused Firebase DB from the Console in the new Firebase? And Google did not help with an answer, which is kind of a first.
Another way if you don't want to delete the project, and just the database, is to create a file on your computer empty.json like this:
{}
Then click on the ... and "Import JSON"
Then "Browse" and upload your empty file:
You overwrite your database with an empty JSON file, effectively "deleting" the old database.
THIS DELETES THE ENTIRE PROJECT
To delete ONLY the database just delete the top level object/node.
Click on your project (the white box below, hiding name):
Then click on gear (settings) icon and click "Project Settings":
Scroll to bottom and click "DELETE PROJECT":
It's currently not possible to delete other Realtime Database instances created via Firebase Console.
They do have plans for adding the feature,but It'll come in the future.
For now, you can watch their updates here:
https://firebase.googleblog.com
https://firebase.google.com/support/releases
Their support suggested me to wipe all data and to lock down the database to prevent any usage, as a work-around for now.
Just remembering that having multiple instance is only possible if you have a Blaze account.
Looks like Google recently introduced this feature to delete a Firebase RTDB. To delete this (after we raised this concern with Google Firebase team on Firebase RoadShow India 😃).
To do this, follow these steps:
Go to your Firebase RTDB which you want to delete
Delete all your data from the database
Select the 3 dots on the top right corner
Hit the "Disable Database" button
After the database is disabled, hit that 3 dots again and click "Delete Database"
Cheers!
If the dots method doesn't work then here's another option-
Open the project you want to delete.
Go to setting (on the left side of the page|near Project Overview).
Select project settings.
You'll find delete project option at the end of that page (below app config).
Then you'll be asked things about the policy of deleting the project and your preference and stuff... you can answer accordingly.

How Do I Remove This Error in Firebase: "This domain is already in use."?

I'm trying to add a custom domain to an existing project but keep getting the error that "this domain is already in use." I'm not using this domain anywhere else in any other project.
There is only 1 other forum post (http://grokbase.com/t/gg/firebase-talk/165r5n78nq/firebase-domain-is-already-in-use) about this error but following the step provided leads to zero results.
If you are getting that error it means that you're already using the domain in a project. You probably deleted the project but did not disconnect the domain before it was shut down. In this case, you can either wait for 10 days from when you deleted the project for it to be removed or,
you can restore the project by going to the Firebase IAM & Admin console click on projects pending shutdown.
Then proceed to disconnect the domain from the project like you normally would. Now you can use that domain again with no problem.
Go to https://console.firebase.google.com/iam-admin/iam/project and click on 'Projects Pending Deletion" click Restore. Then go to https://console.firebase.google.com/project/YOUR-PROJ-ID/hosting/main and delete the domain connection(s).
That should free the domain up for a new SSL cert.
if you are using appname.page.link make appname uniqe

Can't upload to app store due to a missing screenshot

Status of my app is ready to upload
I upload but I forget to add one screenshot.
No problem. Just upload again.
However, the status of my app now is no longer "ready to upload" but missing 1 screenshot.
Hence, when I tried to upload again what I got is:
Applications must be ready for upload on iTunes Connect before they
can be validated or submitted from within Xcode.
What should I do? I know I was missing one screenshot. I already add that now. So now what? I can't upload that screen shot if I can't upload the app. I can't upload the app because the status is "missing 1 screenshot" rather than ready to upload.
You need to go back to iTunes Connect and edit the meta data and/or the data of your application to add that one missing screenshot and that should set the status to "Ready to Upload".
In iTunes connect, select binary detail.
After that select reject this binary.
Then click ready for upload.
Tada status goes back to the way it used to be.

Session State - multiple browsers

What is the best way to keep session state between browser tabs?
I have the following scenario. I have a page where the user opens a 'project' from a grid.
I keep this project in the session as the "Current Open project".
The problem is that users can open another project from another tab in the browser. Now, they open another project and this becomes the new "Current Open project".
If they go back to the first page ... it is clearly a problem.
Is there a way to solve this situation please?
Thanks,
Joseph
No, you just have to handle it.
When a page tries to do something with a project, the server has to check if it's the current project that the page is trying to change or a different project, so that the server can send an error message back that the wrong project is opened.
Alternatively you can avoid keeping the current project in the session, and allow multiple projects to be opened simultaneously. As long as each page keeps track of which project it is handling (which you have to do anyway), it's not a problem.

Resources