-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Crash when invoking a second (different) signature of an overloaded method (meta generator cache?) #555
Comments
Hi @EddyVerbruggen, I coulnd't reproduce your problem.
which looks like an application error. |
@EddyVerbruggen, thank you for the feedback, I managed to reproduce your problem and we'll take a look. EDIT: @EddyVerbruggen, thanks for reporting this issue, the fix will make it into the next release. |
That's fantastic! Thanks for checking and fixings this so incredibly quickly! 🎉 |
2.3.0 FTW!
🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉 |
Tell us about the problem
I'm trying to extend the Firebase plugin with the ability to remove listeners. On Android the Firebase SDK offers the following method signatures (found here):
So these methods either expect an implementation of the
ChildEventListener
orValueEventListener
Interface.Whichever is called first succeeds!, so when first calling
removeEventListener(myValueEventListener)
all is fine, but if I then callremoveEventListener(myChildEventListener)
the app will crash (and vice versa!) with the following stacktrace:My guess is something is cached and the runtime expects the same signature for the same method the next time.. which is not what the Firebase SDK wants me to pass in..
Please provide the following version numbers that your issue occurs with:
Please tell us how to recreate the issue in as much detail as possible.
Those last two steps can be reversed with the same outcome.
The text was updated successfully, but these errors were encountered: