I accidentally deleted the user pool with the user that performs all the amplify operations. Named aws-amplify-admin, which I believe, created automatically once I have created the amplify app. When there is no user I can't access the app through the console nor through the cli.
How can I recover from this situation ?
Disabling and re-enable the studio. This should recreate the amplify-backend-manger user pool with the aws-amplify-admin user.
Like show in this image
Related
As per the Firebase documentation, the contents of google-services.json are considered public. These can be easily retrieved by decompiling the apk.
If so, is there a way to prevent apps from registering with my Firebase project?
I understand that the registration works on the basis of package name. While it's not possible to publish an app with a duplicate package name, for development it is very much possible.
I created a dummy app, and my dummy app successfully registered with my production project. So, looking for a way to prevent that from happening.
You should be connecting your app to Firebase Emulator for local development.
You can go to Firebase console -> Authentication tab -> Sign-in Method tab, and remove localhost from Authorized domain, that way your app will never connect to production DB.
I wish to run an App Maker application as a specific user and have created an account specifically for deploying with "run as the developer".
Using my normal account I have no issues deploying but when using the new account I do not get any options presented for Cloud SQL. As this user is not able to choose either option then it is impossible to deploy the app.
The following has been checked already
The new user has the same application rights as my normal user within the G-Suite admin console.
The new user has editor rights to the App Maker project (is owner).
The new user has owner rights to the GCP project that hosts the default Cloud SQL instance.
The default Cloud SQL instance is the same for both users.
Is there anything I am missing that could cause this behaviour?
For logging purposes I´d like to print to console or even display the current deploy ID (or message) of my firebase web app that is being accessed by the browser.
Firebase Hosting recently released a new REST API. You can use sites.releases.list to see what version is currently deployed.
Old answer:
Firebase deploy IDs don't appear to be available anywhere via programmatic access. The CLI doesn't support listing current or previous deploys.
My recommendation would be to go in the other direction. Have your source code in a vcs like git. When you build and deploy a new version set the vcs hash or version in the deployed code and as the message for firebase deploy. You can then log the log the source version in your code and you can manually associate that back to a release in the Firebase UI.
I set up a new project with Firebase and enabled Crashlytics crash reporting. My Firebase console is showing crashes (so I know the SDK is configured properly):
However, when I click on the crashes, I'm presented with this dialog:
Ok...but this app doesn't exist in Fabric, nor do I have a Fabric account (actually - I did have a Fabric account, but deleted it). AND if I create a new Fabric account, there is nowhere to "add" an app anyway. What am I missing?
Make sure that the Firebase app is connected successfully before trying Crashlatics.
Complete the steps of adding Firebase, probably you were forcing the crash which disabled the Firebase from connecting to the console.
If I have an app already hosted on meteor and I re-deploy an updated version of the app, will all the values in the mongodb be wiped out?
Short answer: No if you redeploy your app, then your data will be kept intact.
It will only be deleted if you delete it yourself. See Meteor app — resetting a deployed app's DB