Skip to content

Update SDK, allow Facebook to use Chrome Custom Tabs #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 11, 2016

Conversation

samtstern
Copy link
Contributor

Fixes #214

@amandle please review

Change-Id: If37b630e311a5b6fcb329cfa8daf57a65dea29e8
@samtstern
Copy link
Contributor Author

PTAL

@@ -9,6 +9,16 @@
-->
<string name="facebook_application_id" translatable="false">CHANGE-ME</string>

<!--
To enable Chrome Custom Tabs for Facebook Login on devices without the Facebook app
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little unclear here. If they don't want to enable Chrome Custom Tabs can they do nothing and have it work? Or will it try to use fbYOUR_APP_ID as the facebook_login_protocol_scheme and break.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my testing when you have a misconfigured custom tabs setup (scheme = fbYOUR_APP_ID) it acts as if you had no custom tabs setup and falls back onto the normal webview flow.

Likely the FB SDK asks the system to handle the URL with your App ID, the system says there are no registered intent handlers, and it falls back.

@amandle
Copy link
Contributor

amandle commented Aug 11, 2016

LGTM

@samtstern samtstern merged commit 429897d into firebase:master Aug 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants