Google API Console - Reuse deleted project ID - firebase

I have accidentally deleted my project at Google API Console and when I try to recreate it, It doesn't give me it's previous ID and attaches unwanted numbers at the end of it.
Is there any way to get that ID back?

If you have deleted a project on Google Developer console. You will get an email from Google something like this.
Dear Google Developers Console User,
You deleted the project “BigQuery” on Jul 16, 2015 6:33:44 AM PDT. If
you still want to delete this project, you don’t need to do anything.
The Google Developers Console team will remove your project
permanently one week from the time of your request.
If this project shouldn’t be deleted, you must visit the following URL
before Jul 28, 2015 12:50:21 PM PDT.
https://console.developers.google.com/project?pendingDeletion=true
After Jul 28, 2015 12:50:21 PM PDT, the project will be inaccessible
and can no longer be undeleted.
If you have any questions, please visit the Google Developers Console
Help at the following URL, or contact support.
https://developers.google.com/console/help/new/
Thanks, The Google Developers Console Team
If you ignore that email and allow the time to run out. Your project is gone and I have never known anyone to be able to get it back after that date. Check your email if you are lucky the date hasn't expired. If not your project is gone and you need to create a new one with a new project id and accept the consequences of deletion.
IMO: I really wish they would add a lock to projects so we can prevent ourselves from deleting something we really really should not.

Google project id is system generated and once the project is already deleted, you can't have the same id as before. I suggest you to check if the project is already "shutdown", because I believe that there's a 7 day grace period to recover it. Check out this google help documentation.

Related

Unexpected error when querying Google Play Developer API

We have been trying to set up the sample app for Play Billing workflow with subscriptions as we are looking to introduce subscriptions in our app. We wanted to have the ClassyTaxi app running end to end in order to understand the flows better. Although for past 2 days, we are only trying to debug issues and/or missteps because of some really poor documentation on Google's front.
After ensuring every single step was correctly followed, we were able to make some progress and have the app working with the correct Skus as configured in Play Console. But now the backend server (ClassyTaxiServer) is throwing below error:
"Unexpected error when querying Google Play Developer API. Please check if you use a correct service account" - "OtherError: The project id used to call the Google Play Developer API has not been linked in the Google Play Developer Console.".
We have relooked, recreated the service account on the Cloud Console several times, but no luck.
The Play Console is correctly linked with the Google Cloud project and the access is correctly granted to the service account.
Anyone has any suggestions? How can a sample app be so difficult to set up and function as expected? Or are we doing something terribly stupid?
Please help.
Thanks.
I passed trough similar situation, and I get same issue. After checking I found a note in google documentation saying the following:
Note: As of December 1, 2019, the Google Play Developer API is available only for version 3 and higher. If you're using a lower version of the API, you must migrate to version 3 by this date. For more information on migrating to version 3, see Changes to the Google Play Developer API.
Investigating the implemented code I found that the sample uses v2 of the google API (check ./subscriptions/play-billing/PlayBilling.ts line 70). So to avoid this situation, you will need to set it to v3, and update googleapis dependency to latest version in package.json.
Additional Notes
After solving this issue, I had a different message in 'OtherError', this time is “The current user has insufficient permissions to perform the requested operation.”. I will note my solution here just someone passed through similar situation:
In google play console, and after clicking on 'Grant access' in 'API Access' tab, you will need to select the user and add some permissions to the user (in my case I set it to admin, but I think it's larger than needed), make sure also to add the app/apps you are listening to.
If the issue is still running, just edit any of your products or just try creating new one, this step will clear the google cash and refresh permissions. (Check this question).

Previewing failed, but deployment works

Background:
I'm quite new to App Maker, but have been involved in programming/IT for over 2 decades.
I have created an App Maker app, which works fine. It is deployed, and functions internally in our organization.
It accesses a Team Drive spreadsheet, makes modifications to it based on input criteria, and sends an email out to a hardcoded user. It uses no external GCP database or other resource.
The OAuth scopes it requires are:
admin.directory.user.readonly
drive.readonly
script.send_mail
spreadsheets
userinfo.email
Problem:
I can no longer preview the app.
When I click on "Preview" at the top right, a new tab opens and a spinning wheels seems to indicate that the preview is loading. Within about 4 seconds, the tab closes and the original tab (with the scripts, UI etc) gives a "Previewing failed. Dismiss" error in the bottom centre.
I am both able to deploy the exact same code/UI/etc, as well as run it without issue.
I do not know what I changed, since being able to preview the app, but cannot seem to regress to that state.
What I've tried:
Admittedly not much, as I don't know where to look. I'm rather certain that there must be some setting somewhere, but for all my googling, I've come up empty.
This can't be a client/server script or other syntax issue, as otherwise the deployment also wouldn't work.
With a more meaningful error, I would know where to look.
Expected Result:
Obviously, I should be able to preview the app if it is deployable.
Following #Morfinismo's comment, I contacted G Suite Support; my matter was escalated to the API Team.
I was asked by Google Cloud Support ("Support") to provide network traffic info using FiddlerCap. As I am on a linux machine and FiddlerCap is a windows application, I suggested alternatives (eg:Wireshark). It was eventually not required and never provided.
I noticed that on the Google scripts page, when accessing the project in question selecting "Preview", it was missing the following OAuth:
https://www.googleapis.com/auth/admin.directory.user.readonly
The functioning deployed version did not have this missing.
Still in the Preview, I selected "Stackdriver (logs)", which gave me an error that the project had been deleted. The actual wording was:
Access forbidden
Project XXXX is shut down and scheduled to be deleted. A project owner can cancel the shutdown on the projects list page.
Clicking on the link in the error "Go to projects list page" brought me to a page with the title "Resources pending deletion", which did not load a list of projects (but otherwise fully loaded) and would display the spinning wheel in perpetuity. I attempted this multiple times, including leaving it overnight once.
Support presumed that I had deleted the GCP project, although I honestly don't/didn't think I had. I also confirmed that creating new previews did not work, but creating new deployments did. I also confirm(ed) that this particular App Maker app did not require (eg) a GCP SQL database.
Support pointed me toward the following website: Google undelete project and I was asked to follow these steps (copy-pasted here):
a. For projectId, enter your project ID. From the screenshot you provided, this is "XXX (redacted)" (the quotes are just to emphasise the project ID, you shouldn't enter them.
b. Click EXECUTE.
c. You'll be prompted to grant authorisation, which may be preceded by a prompt to choose your admin account. Please do so.
d. You should receive a 200 response, with an empty body, that is {}.
e. Attempt to access the project via Project link (with the actual project id redacted here).
The above yielded some strange behaviour:
a. undeleteing the project gave it a different name that the App Maker app;
b. I notice that I had 3 other projects all called correctly (the App Maker app name).
c. When asked to reauthorize, I was provided with yet another project name ("Untitled project"), which was different from the correct one and different from the one in para. 7a, above.
d. I then also obtained another error in a new window which read:
That's an error
Request Details
(a bunch of stuff)
That's all we know.
Support advised that there may be a propagation issue, and that I should wait up to 30 minutes. I did, and it then worked! The only weird thing was the project name was wrong, but it was only for the preview, so I didn't really care.
If anyone needs additional information, I can PM screenshots I took along the way.
Hope this helps someone!
SJL

Access my projects details in Microsoft Project server 2013 errors?

I have created one PWA(Project Web App) site in MS Project server 2013
I created projects on it it was working fine,
but after some time when I wanted to access my projects details page
it give a loop error:
An error occurred while opening your project. Give us a few minutes and try again. If this happens again, contact your administrator.
can anyone tell what cause the error in MS Project Server 2013 Web App
Have you checked permissions in Groups & Categories? It could be as simple as needing to add "Open Project," "View Project Site" "View Project Schedule in Project Web App" and "View Project Summary in Project Center" (in Categories).
I have had weird permissions issues cause such loops. It would be a good place to start if you haven't already investigated.
This issue most like occurs as a result of values being changed for custom field lookup tables. If you know what lookup tables have been modified, consider updating the tables and try again.
If you have access to the ULS logs, the details may provide you with a better insight to the actual data error.

Need to transfer app build from developer to myself Bundle ID and Provisioning Profile transfer?

I had an app created for me--Demeter's Harvest (iOS). The company that built it has dropped off the map, so I can't get them to help me with this.
I get a message when I try to access it all that reads: An App ID with Identifier 'info.NAMEOFDEVELOPER.demeter' is not available. Please enter a different string." and another one for the Bundle ID that shows the Identifier 'info.ORIGINALDEVNAME.demeter' with the version and build.
I placed my name into the team area, and got a message that says no non-expired provisioning profiles are installed with a "Fix Issue" button.
How do I go about gaining access to my app code (if that is what it does) so I can get a new developer to make changes and updates to it?
Thanks,
Ed
You're likely up a creek here. If you don't have your app code there's no way anyone can help you gain access to it except the developer.
Regarding the bundleID it will be tied to whichever Dev Portal created it. If you own that portal you're fine. If the developer owns that portal and they either don't renew their account or block you from accessing it there will be no way for you to re-use it.

Air Application affected by Computer's Set Date

I'm working on creating a 30 day free trial of my Air app.
When the 30 day trial begins the current date is stored in the local encrypted database. Then the date is checked against the current date if the difference is 30 days or more the application denies access and the users is prompted to purchase a license.
It seemed I had have everything working fine but I just ran into a problem.
I changed the date on my machine which made my Air app think this was the current date, allowing the 30 day trail to still be active.
I'm wondering what the workaround might be to fix this? Is it possible for Air to get the current date not based on the computers set date?
If you application has logging to a file system, preferably a sign-on logging event, write a file or update a file.
Prior to this writing step, do a check in that directory to see if any of those files are dated in the future. If they are, the user has rolled back their system. Flag it.
Try not to use sharedObject cause that I might get blowaway. Alternatively you can update a table in SQLite or whatever persistence mechanism you are implementing in your app.

Resources