I'm trying to set up Facebook in my android app but I had a problem and even the samples didn't work ! Then I tried again on different devices and I just figured out the samples only work on devices which do not have official facebook app installed. It seemed to me completely illogical so I checked : installing the Facebook App and it wasn't working anymore, deleting it, it worked fine then no issue. So here my question : Why is that and how to fix it when Facebook Official App is already installed in device ?
Looks like you have not added key hash to app dashboard or it is invalid. To properly handle Facebook Login using the Facebook for Android app you will have to add valid key hash to the app dashboard. Have a look at this: https://developers.facebook.com/docs/howtos/androidsdk/3.0/login-with-facebook/
check 'App Dashboard Configuration' and 'Troubleshooting' sections.
Related
AWS Cognito Federated sign in with Google setup correctly and it works perfectly on Android devices (phones, tablets). But on Android TV Web Browsers can't redirect to custom url scheme (web browsers don't understand that the app should be opened). The error says "can't open scheme myapp://oauth/?iod=..." with the error code Net::ERR_UNKNOWN_URL_SCHEME.
React Native version is 0.66, with not the latest aws-amplify, but the issue mainly related to the behavior that browser doesn't open the app with custom url scheme.
Does anybody encountered such an issue and if yes, then what solution could be here?
Appreciate your help.
I've tried to use redirectSignIn url as App link instead of custom url scheme, but that didn't work (when you open app link from another app android opens proper app, but if redirecting/opening within the browser, then it redirects to the web page).
So I have Google AdMob implemented in my Expo React-Native app and everything is working fine. I got this alert two days ago in AdMob console, I have been googling for the past two days but cannot find any answer to:
How to enable enable SKAdNetwork to track conversions https://developers.google.com/admob/ios/ios14?hl=en-US ?
Do I need to do anything?
Some apps haven't been configured to use Apple's SKAdNetwork
To ensure you're getting credit for all ads activity, like app installs, be sure to configure SKAdNetwork with Google's recommended network IDs.
I have a react native app with admob, my app-ads.txt is present and validated by Google. The app is in PlayStore, everything works fine.
I added Facebook login button for the new version, I created the app on Facebook developer dashboard, but there is a section in general settings that asks me to confirm the ownership by adding a line to my app-ads.txt. If I don't pass this step, I can't put the Facebook app in live mode.
Even if I don't understand why I have to do it since I do not advertise on Facebook with this app, I added each of theses lines, and tested them one by one, and each time Facebook tells me that an error has occured and it can't proceed.
facebook.com,MY_FB_ADVERTISING_PERSONAL_ACCOUNT_ID,DIRECT,c3e20eee3f780d68
facebook.com,MY_FB_ADVERTISING_BUSINESS_ACCOUNT_ID,RESELLER,c3e20eee3f780d68
facebook.com,MY_APP_FB_ID,RESELLER,c3e20eee3f780d68
facebook.com,MY_APP_FB_ID,DIRECT,c3e20eee3f780d68
Just to be sure that FB has the good url, I renamed the app-ads.txt file on my server, FB tells me that no valid file was found. So, there is no problem with the url or the developer website declared on the play store.
The problem is surely in the file content, and I can't be sure which line is good.
Does someone has an idea?
Details: The new version (with fb login button) is not in the playstore yet, there is only the fist one, does it matter?
I’m trying to setup the Google authentication using AuthSession in Expo documentation (without Firebase)
https://docs.expo.dev/guides/authentication/#google
The first problem is, that the slack example doesn’t work: on the devices and simulators nothing happen after pushing the button, and in web mode it returns an error
Error 401: invalid_client
The OAuth client was not found.
What I’ve done using steps in documentation:
I’m not sure if it’s necessary, but I’ve installed yarn add expo-application
I’ve registered in Credentials page (Google Cloud Platform)
Logged in using expo login, in the terminal where I was starting expo start
Created a new Google Client ID that will be used with expoClientId
(Image) New Google Client ID setting image
( I'm not allowed to input images now )
(Don’t know if it’s necessary) I’ve created a project in https://expo.dev/ and then published the project using dashboard of expo start
(Image) Setting for "publish" in expo start dashboard
Where:
“expo”: {
“name”: “rn-my-project”,
“slug”: “rn-my-project”,
“version”: “1.0.0”,
“orientation”: “portrait”,
…
}
Using the code in the example, provided in documentation for Google, I receive null as response.
As I understand, this should be enough to test the Google Authentication using AuthSession in Expo Go app. I also made iosClientId, androidClientId and webClientId, but I’m not sure if I made everything correct.
Will be glad for any help, because I couldn’t find any person with the problem as mine.
Yours sincerely.
P.S. I've successfully set up logInAsync for Google using this documentation, but it's written, that it is deprecated.
I am using Branch.io to send users their credentials in my app. Since the app is not live yet, i am testing with everything on "live" in the Branch settings.
If I create a link from the app and send it via Slack or email, with the app installed then the app opens but if I share the link with Facebook messenger then the fallback url is used. EDIT:The fallback is the expected behavior on iOS, but i am working on Android.
I did find this which (1) is not very promising (2) is old (3) is not exactly the same situation since the links do work for me.
If you click the link from the Facebook Messenger app, then redirecting to the Fallback URL is the expected link behavior:
https://docs.branch.io/pages/links/integrate/#expected-link-behavior
Per the docs, you can still open the app using URI schemes or a Deepview.