I'm using Firebase-Invites cordova plugin.
I'm able to use FirebaseInvites function and send invitations successfully. The links are generated with my associated domain, but when I click on them, Google Services keeps restarting and shows a spinning wheel, and nothing else happens.
The example link generated by FirebaseInvites:
apnXX.app.goo.gl/i/IZsum
When I generate a dynamic link on Firebase console, the format is slightly different:
apnXX.app.goo.gl/xxxxx
The link that I generate on Firebase console works correctly and opens the app.
Any ideas as to what am I missing? I'm testing this on Android.
Related
I have been building an app in React-Native using Expo and I am getting ready to upload beta versions for iOS and Android. I am using 'Facebook Sign in' and while developing and using the Expo Go app, I had no issues making it work. However, on Android, after making a native build, Facebook is no longer working. The authentication modal pops up, asks for the user's login info, but then it just hangs on a blank screen. No error and the modal does not dismiss. I am using the Facebook provider in the 'expo-auth-session' package for this but I think the problem lies in the Facebook Dev Console. When I try to add an android platform to my facebook account, I provide the key hash with no issue, but when I try to add my package name (as it is defined in my app.json file) I get an error saying "There was a problem verifying this package name". And if I try to press the "Confirm Ownership" button, I get another error saying "Error found while validating app-ads.txt". The problem is, I don't have my app listed on the google play store yet because I want to test it as a native build rather than inside the Expo Go app. I'm not sure if this is what is causing the Facebook sign in to not work in my native app, but I have followed all the other documentation provided by expo and this is the only issue I have run into. Is there a way to verify my app package name before submitting to the Play Store. And do I actually need to have an "app-ads.txt" file somewhere in my project? I currently do not have ads or any form of monetization in my app.
I have a Flutter app and i need to detect the url that originated the app download in the stores. On android, i send firebase dynamic link X to some user, he opens it, the OS tries to open the app if installed or redirects to a landing page if not. Then in this page there is a link to Play store. If he downloads it, on first run the app detects correctly that it was launched from link X. So far, so good. For android, all i need to do is upload a test version of my app to play store and set my user as tester, so when the store link is opened, it shows the internal testing version instead of the production one. The problem is: on ios, i have not found a way to link directly to a test version on App store (everythng is handled inside test flight app), so i´m unable to test the whole process. Is there a way to replace the store link app with a test version for specific users?
I have an angular/ionic website that has registration, login, and dashboard pages. I want to build an android & ios app with the same code base.
When users download the app from the play store, if I add a new page/make a change to the existing page I have to submit the app for review, and then it will show the option for the update. Also, the user may not update the app. I want to show the latest changes to users as soon as I am ready with the update.
To achieve this I have followed the below steps:
1.I have built and deployed a web app(without native code). Let's call it xyz.com
2.I created a new ionic project for the APK file. I have placed an iframe with src=xyz.com
When I take the APK build of a new project, because of the iframe tag I can see the complete web app loaded. Whenever I make changes to the main web app project, after deploying to xyz.com just reopening the mobile app I can see the latest changes.
3.I have to read OTP during user login. So, after validation of user credentials in the web app, the next step is to enter the OTP. Now I have sent the event from the web app to the parent window(mobile app) like this:
window.parent.postMessage('ReadSMS','*')
In the mobile app, I listened to events from the website loaded in iframe like this:
window.addEventListener('message', handleMessage, false);
function handleMessage(event) {
if(event.data === 'ReadSMS'){
// Start native plugin cordova-plugin-sms-receive to read incoming sms
// After reading the SMS it is sent to the web app(in iframe)
myIframe.contentWindow.postMessage('SMSResult', '*',{OTP:otpfromsms});
}
}
In the web app, I listen to the events sent from the mobile app and auto-populate the OTP in the input box.
With the above iframe approach, users can use the new pages/bug fixes without updating the mobile app from the play store.
Since I use very less native plugins and they are not changed frequently. If I make any native code changes, then users have to update the app from play store, I am ok with that.
We have a tool called Ionic Appflow which has Live Update feature lets you update the UI and business logic of your app remotely, in real-time. Push HTML, JS, and CSS updates directly to your users without going through the app store to instantly fix bugs and ship new features.
The ionic Appflows is a paid tool and we can't afford it. However, I'm able to achieve live update feature and native functionality with just iframe and window message events.
Is there any disadvantage in the approach I have taken? Will, there be a problem while getting approval for listing my mobile app in the android play store and ios app store?
Can somebody please tell me the cons of the approach I have followed.
Thank You
I am currently developing a sample TV app to perform in-app search using google assistant. I created an agent in dialogflow and also coded the fulfillment part.
In order to perform app linking in my sample app, I followed the steps provided in android developers site. I have secured website to link my app.
According to the procedure, I created the assestlinks.json file using the app links assistant in android studio. Placed the file at the root folder of the domain as well i.e, "https://domainname/.well-known/assetlinks.json". But when I click on "link and verify" button in app links assistant, the error "We could not associate your app with the selected domain.Please make sure the Digital Asset Links File is uploaded to the correct domain" displays.
But when I click on the link,I am able to see the file at that location.
Please help me in correcting this issue as I am not able to proceed since a long time due to this.
To use the Assistant for in-app search, you need to use a content provider. With your content provider, you specify the deep links explicitly in the search results.
https://developer.android.com/training/tv/discovery/searchable
For more details about how the Google Assistant works on Android TV check out this blog.
I have read your README.dm from the firebaseui-android library. Can be found https://github.com/firebase/FirebaseUI-Android. This will be the first time that I have used your Authentication for getting a user to login. I am currently only using the Google sign-in, but will add Facebook and Twitter in the future. In this README.dm keys section github.com/firebase/FirebaseUI-Android#add-facebooktwittergoogle-keys this is the only instructions for the Google sign-in.
If you're using Google authentication, place your google-services.json in the app folder.
There is no mention of having to setup anything else for the Google sign-in to work. But at least in my app for the Google sign-in to work I needed to also setup the authentication for a web app which can be found www.firebase.com/docs/web/guide/login/google.html#section-configure. But if I configure the Web app authenitcation then I don't need to google-services.json. Why is your library not using the google-services.json but instead only using the web app. This is not a web app as it is a native Android app. I think that this also leads to the user being logged out if they do not use the app after the expiration unix time returned in you authData.
All I want to do is log a user into my app using either Google, in the future Facebook or Twitter, and not have to have them re-login if they don't use my app for a few days. If you library cannot log a user in using the native and keep them logged in then I guess I will have to write the login myself.
I don't really know for sure what you want but I think the Firebase team was trying to make the document more concise for everyone. You have to do some of the work yourself.
So I will just drop this links and run
Create a project in Google Developers Console https://console.cloud.google.com/project
Click on "Get a Configuration File" https://developers.google.com/identity/sign-in/android/start
Know that I did not (actually, could not) give you all the information you may need because I am also working on something. Just like you.