I'm using Firebase dynamic links for referrals in an Expo app (managed workflow), but the link data isn't surviving the app installation process. The links worked fine when testing with a standalone app: when the user didn't have the app, they got directed to the App Store/Play Store* and when they did have the app, the link was handled using Expo's Linking.getInitialUrl().
I've actually gone ahead and published a native binary that displays a modal with the link data upon signing up to the app** (again, using Linking.getInitialUrl()). The modal only displays the app's custom url scheme myapp://. This same test displayed the link as expected when testing with a standalone app.
Note that the links work as expected if the app is already installed.
*This answer seems to suggest that this is enough to ensure the data will pass
**Fortunately we are very early stage with no users lol
Related
please can i get some help about , firebase distribution from codemagic ? When i finished building the app , i don't know why it doesn't publish himself to firebase. It always give me an error , like it show below here:
In tried to resolve the problem by trying to associate it to google play , i saw here https://support.google.com/firebase/answer/6392038 , but i am not getting even the possibility to associate , like it showing down here:
check you completed following steps:
The app is registered with your Firebase project and your Google Play developer account. This means that you have both a Firebase Android App and a Google Play app.
The app in Google Play and the Firebase Android App are both registered using the same package name.
The app in Google Play is setup on the app dashboard, and it has the following status:
The app is distributed on one of the following Google Play tracks: Internal testing, Closed testing, Open testing, or Production.
The app's review in Google Play is complete and the app is published. Your app is published if the App status column displays one of the following statuses: Internal (not Draft Internal Testing), Closed testing, Open testing, or Production.
I started to distribute application by Firebase App Distribution using AppBundle instead of APK. But when testers are trying to download build from "App Tester" application it opens Play Store but it opens "Internal beta" page, not Internal App sharing page with this build. Clearing data of Play Store application helps and they see correct Internal App Sharing page with correct build, but only once, when they are trying to download another build it opens "Internal beta" page and they need to clear data again.
I checked on my phones, on two test devices where I have only one authorised account in Play Store, everything works fine. But on my personal device where I have two account I see this issue. Testers have only one account on device but also have this issue, so I don't thing that the problem with amount of accounts.
Has anyone had this issue before and can help me resolve it?
I have an RShiny app that I had published online without any issues until this week. The app uses data stored in a Google Drive account, thus making use of the googlesheets package. When the app was working fine, I used gs_auth() to initially authorize and cache my Google credentials. Because my credentials were cached in a .httr_oauth in my working directory, it meant that when I ran the app's code, it wouldn't take me to a page in my browser that would ask me to authorize the account. When publishing the app to shiny.io, this cached .httr_oauth meant that the app would work online.
This week I made some changes to the app's code and when I ran the app it took me to the Google account authorisation page. There, I would click on the account and it would then say: "Sign in with Google temporarily disabled for this app".
After some looking I found that the googlesheets package is now outdated and I should instead be using the googlesheets4 package. However, after trying to authorize with that package (and the googledrive package) I'm able to get the app to run locally without it taking me to the Google account authorization page, but when I try to publish it still doesn't work. It always times out. Does anyone know what is going on? Anyone else having a similar issue?
I ran into this problem as well.
This outline worked really well for me.
https://gargle.r-lib.org/articles/non-interactive-auth.html
I would focus on Project Level OAthu part of the vignette.
The biggest issues I had for switching from "googlesheet" to "googlesheets4" was I forgot to install the "googledrive" package. The googledrive will allow you to use (drive_auth) and then build out from there as you can cache the authentication token.
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
my starting point is html5 code (which works fine when served to a browser). To then build an iOS app, I'm not using phonegap locally, I just upload to phonegapBuild, install my apple credentials, and attempt to run the app on my iphone. The app loads, begins to execute, and then presents a popup saying that google does not like my API key.
The key is of type 'simple API access' pointing at my iOS app ID.
I am presenting the key in the head of the .html when I request the google maps v3 API. I suspect this is wrong based on the instructions in [https://developers.google.com/maps/documentation/ios/start] referring to an xCode built app: "Finally, add your API key to your AppDelegate." I am trying to avoid xCode. I'm thinking there must be some config.xml magic necessary to pull this off.
So, how should vanilla html5+config.xml present a google API key to phonegapBuild to build an iOS app?
(please see screenshots on [http://community.phonegap.com/nitobi/topics/how_should_google_api_keys_be_handed_to_phonegapbuild_for_incorporation_into_an_html5_based_app_for_ios] )