Skip to content
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

[Known Issue] NoSuchMethodError: No virtual method launchUrl #398

Closed
samtstern opened this issue Nov 6, 2016 · 7 comments
Closed

[Known Issue] NoSuchMethodError: No virtual method launchUrl #398

samtstern opened this issue Nov 6, 2016 · 7 comments

Comments

@samtstern
Copy link
Contributor

There is a known issue in the 1.0.0 release that can occur when using Facebook login with the optional Chrome Custom Tabs configuration and support library version 25.x. There is a fix being discussed in #396.

Some known workarounds:

  • Do not use Chrome Custom tabs with Facebook login
  • Downgrade your application to support libraries 24.x

If the above workarounds do not solve the issue, please chime in so we can further diagnose.

@samtstern
Copy link
Contributor Author

The fix for this issue has been released in version 1.0.1.

@lawloretienne
Copy link

I think this is still an issue with Custom Tabs
http://stackoverflow.com/questions/40319860/com-android-supportcustomtabs-no-virtual-method-launchurl

This is still an issue with the following dependencies : compile "com.android.support:customtabs:25.0.1" and compile 'com.facebook.android:facebook-android-sdk:4.19.0'

@SUPERCILEX
Copy link
Collaborator

@lawloretienne you're mixing support library versions. Please use v25.1.0 to use the same version as FirebaseUI and see if that fixes it.

@lawloretienne
Copy link

so i'm not using firebase at the moment, but i noticed this same issue of facebook login and custom tabs was documented here.

@SUPERCILEX
Copy link
Collaborator

@lawloretienne Got it, check out our build.gradle file. You basically need to include all of the support libraries Facebook uses and override them with the version of the support library you are using to prevent incompatibilities.

@lawloretienne
Copy link

Got it. That worked. Looks like these dependencies can get very brittle sometimes. Wish it wasn't the case.

@SUPERCILEX
Copy link
Collaborator

@lawloretienne Glad to hear the issue was fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants