Issues with losing all documents when going to deployment url - google-app-maker

I wanted to share with other users in my company a Google App Maker app I have been developing. When I develop the app and use Preview, my data is all kept.
But I know I can't use the preview url for other users to access the application. So I Published the app and got a deployment url I could give to other users. The problem I am having is that all documents created are gone for myself (and I assume the other users) each time I open a new window with the deployment url.
How can this be fixed. I am thinking there is something silly I am missing or doing.

I experience the same issue, but I think this is because when using Google Drive Tables, they are local to the app instance. So your development app tables are not the same as the published app tables. Also, if you Published your app twice, it would be 2 different sets of tables (I think). There is a way to import/export data, so you may want to export the data from your development tables and import to your published tables.
Google App Maker Import and export data

Related

How can I automate play store app creation

We have a template app written with flutter that each customer can buy a version of it and have the exact same functionality but connecting to a different database etc. Creating an app for each customer and deploying that app takes a lot of time, so we've decided to automate this process. For deploying updates of the apps, I was able to achieve that functionality very easily by integrating fastlane.
The part I am stuck at is how to automate app creation with all the steps (Creating the app, filling main store listing, publishing the first version, etc.). I've searched all over the internet and not found a single solution for this. For the App store there exists the fastlane produce tool, but according to the maintainers they do not plan to support an alternative for android at the moment.
As a solution I'm thinking of doing this using web scraping using tools such as puppeteer or selenium. Is there a better solution, and is doing scraping for this task a bad idea?

How to avoid modifying Firebase Firestore data when working on new version of a app

I have developed an app (my first app) that's currently on app- and playstore. I'm using Firebase/Firestore as a back-end/database. I'm about to start to work on the next version of the app, which will require me to modify my database for testing and such. However, I currently have about 100 regular users on the app and I wouldn't want them to experience any weird data changes on their app while I'm developing.
I'm simply not sure about the way it's done when you further develop an existing app. I was thinking of creating new collections in Firestore simply for testing and hook my app with them but I don't know if that's the best way to go.
How do I work on a new version of an app without my users seeing any changes in their data?
If your data model is (very) simple you could create some specific, temporary, collections as you describe, but this is quite an error-prone approach (risk of modifying existing data, wrong or missing security rules, etc..) and is not recommended.
One standard approach is simply to create another Firebase project which is totally isolated from the production project. You will need to change the Firebase configuration in your Flutter app. If you need existing production data in your test Firebase project you could use the export/import mechanism.

Firebase: multiple Apps connected to single firestore

This is intentionally a very broad question. Sorry about that.
I'm experimenting with firebase for the first time. I would like to build a little e-commerce webapp using firebase, React and Next. I would like to split the App in two different apps: one admin app (used to create products and do other admin stuff) and the actual shop app. The Apps should be hosted on two different domains but they should talk to the same cloud firestore.
What would be a good setup to implement this architecture? Currently I am thinking about creating separate firebase projects for the admin and the shop app so I can host them on different domains. The cloud firestore would live in the admin project together with all admin related cloud functions etc. The shop app (or client app) would have its own project for hosting and would be connected to the firestore from the admin project.
Does that sound like a reasonable architecture or am I completely on the wrong path. Any suggestions are appreciated. And again sorry for the broadness of the question.
You don't need to do anything special. Each app (mobile, web,whatever) connects to a firebase instance/project. You can just set them all up to use the same firebase project (.plist file etc) and it will all work. The advantage of this design is that both admin and client access the same data, which presumably you need. (If you haven't found it, on the Firebase Console -> Settings -> Project Settings; add applications which will generate the appropriate credential files for each device type.)
Since you will have a shared/common authentication space, you may find that you want to add a flag/limitation to login so that only specified users can access the admin side. There's a few ways this can be accomplished.

Download an app from the app store, without the UI

I'm working on a tweak that needs to download and install an app from the App Store (given a bundle id or some kind of other identifier), but doing so without using the App Store app (e.g., to allow the user to remotely instal an app on the device, without going through the App Store UI).
(I'll pause here to point that obviously this has nothing to do with piracy, as I want the app to be downloaded through the user's account in the store, and in any case I'm only targeting free apps at the moment).
I went through iOS 7 private framework headers and couldn't find a way to fit in and to tell the device to install an app with a given identifier. I've also looked for similar tweaks to have a look at their source, but the only one I could find was 'Auto App Updater', and its code isn't public.
I would greatly appreciate your help in coming up with a code that does that, or an open-source tweak that utilises a similar function.
Thanks a lot!
Dan

How can i convert my google analytics web app into mobile app?

I have a mobile apps that i applied my google analytics track IDs but when i create the google analytics app profiles i initially choose web app instead of mobile app. while exploring around the settings, I could not find a switch to convert it into mobile app. I have more than 10 app with different google analytics track id, so i don't think creating new profile is great solution, there might be switch to change it to mobile app.
Someone out there might have encounter this situation. please help.
Solution:
What i did to solved this was create a new App, same name with the web one, then set it to mobile and then delete the web app.
The accepted answer is actually the incorrect. Specially if you have a existing web profile which as lots of historical data. Here is how to solve this by keeping your existing web property.
You add a profile view on your existing Web Property which can be a Mobile Ap Profile. https://support.google.com/analytics/answer/1009714?hl=en
The big clue came from this Upgrade to Universal Analytics post https://developers.google.com/analytics/devguides/collection/upgrade/reference/mobile-sdk
"To get access to new app reports and features, you will need to upgrade to v2.x or higher of the SDK and create at least one app view (profile) in your reports to view the data. Any new data sent from your app will only be available in this new app view (profile), while your old data will continue to be available in the original web view (profile). Learn more about the latest version of the SDK for Android or iOS."
There is currently no way to change the type of tracking after the profile is created. You will have to create new profile IDs and update the apps.

Resources