AppMaker - Google Drive Table not available - google-app-maker

Please refer to my image, "Google Drive Table" option no longer available today (suddenly) ... But i checked back my existing appmaker app, i am still able to create additional google drive table but not new app
Missing 'Google Drive Table'

For the new app it's deprecated. However you can use the one which you have created earlier for now. That also will be deprecated eventually. Refer App Maker release notes for more information.

Related

Error while trying to create Firebase Firestore Database

I am new to Firebase. When I am creating a new Firestore database am getting this error
Enabling Cloud Firestore will prevent you from using Cloud Datastore with this project, notably from the associated App Engine app
All solutions I found online are completely targeting experts/individual who knows their way around Firebase and Google Cloud. To me, this error is a roadblock. I tried using my other Gmail accounts, creating new projects and the same error appears. even the cancel and close buttons seen are not working I have to refresh just to get back.
Kindly help or guide me what should I do.
Based on #JoshL.Minga and #RenaudTarnec comments, the issue was narrowed down to a specific browser. After switching to Safari it didn't reproduce.
This issue has been reported to Google support.
Aside from that, you may want to try creating a Frirestore DB using a brand new project. Make sure that your new project is created via the Firebase console and not in the GCP console.

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).

having difficulty in getting api key and other relevant information in firebase

I just started with firebase and I am having some difficulty in getting api keys and other relevant data required.I am building a web app .
Here is the screenshot of the current screen that i got in firebase .
I clicked on Add project .Got directed to another page where I clicked on Develop ,then database and finally created a realtime database .But i am stuck as how to get relevant api key and other data .
I am following this tutorial
tutorial link
to get my hands on firebase and react.
I believe you are new to Firebase so I'm going to Help you with the screenshots. As Tomka mentioned please read the documentation where it covers all the required information.
1-Go to Console, Select your project(In My Case TestApp)
2-After you have selected the Project, Select Project Settings
3-As you are configuring in the Web app (React), Please click the one pointed in the image.
4-You should have the Details you are looking for something like below

Google App Maker app not working after deploy

I have built an app with Google App Maker which has a Suggest Box linked to a table by a Query parameter.
The app works correctly in Preview mode, but when I deploy it, the Suggest Box doesn't suggest anything!
I have deployed it once before (without a select box as I recall) and it worked correctly.
I tried redeploying to the original deployment and deploying to a new deployment, same result.
Am I missing some security setting or something?
I am using Drive Tables as my datasource. The kind people at Google sent me a couple of links which helped me to understand what's going on: previewing and publishing your application and running as user or developer.
The crux of the issue is that when you deploy an app and run it as user (default), it doesn't take any Drive Table data with it. If you want to add Drive Table data to the deployed app, you have to do this:
Open App Maker
Go to App Settings
Go to Deployments
Select your most recent deployment and click: “EXPORT DATA”
Make sure you select Preview from the Deployments drop down list.
Click Export
This will export all your Preview data to a new Google Spreadsheet.
Now go to your Drive models in the App Maker and click “IMPORT DATA FROM SHEET”
Here you can choose to import data to your Deployed version.
After completing the import process, you will have all your data in the Deployed app.
All courtesy of Google but I didn't find it in the docs, so it might help someone.
Use the browser console to see if there's an error on the connection, make sure the user has access to the datasource and if you're using cloud SQL check the parameters of cloudSQL in the publication

How can I publish an updated version of an AppInventor app when forced to use a new / different certificate/key?

I dabbled with AppInventor a year ago and built an app that I now need to update on the Google Play marketplace.
Im NOW using Flex/FlashBuilder4.6 now and I have the new version of the app all tested and good to go but android developer console shows message stating that It has to be done with the same key...
is there any type of work around here or am I really going to have to just abandon that previous app and re-create a new app entry on Google Play?
I setup a new MIT account when it moved and can see a few test projects in the MIT App Invetor but dont see the app in question so perhaps that all of this is futile. I'll begin thinking I could setup the OLD app to show a message and then link that takes the user to the new app prole on google play but not having the zip file is a deal-breaker... any way around this at all?
Thank
The question is: did you create the apk file with App Inventor only (possible since Version 125, May, 6 2012) or did you use another tool like Marketizer or AppToMarket to sign the app?
In case you used App Inventor only, you could use the same package name of the old project.
The package name for an App Inventor project looks like that:
the first part of the package name is always the same for App Inventor projects appinventor.ai_ then follows your gmail login name and then after the . follows the App Inventor project name
example: appinventor.ai_taifunbaer.caturday
For signing the app you can use the alias=androidkey and key pwd=android, see also here

Resources