-
Notifications
You must be signed in to change notification settings - Fork 578
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
Documentation or nullability annotation of FirebaseDynamicLinks.getDynamicLink() intent parameter wrong #2336
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @ubuntudroid, thanks for your report! The documentation is wrong, since the method implementing that interface does in fact expect the value to be non-null Line 95 in 6ccc9de
I'll follow up here when we have a fix ready. |
b/178000308 |
What is the expected usage when you only care about the captured dynamic link after install? (e.g. because you have your own deep linking mechanism to handle app links that doesn't rely on Firebase Dynamic Links) It'd good to have a |
Added a fix here: #2629 |
This just bit us on react-native-firebase. We were coded up to wrap the API per docs, but a user took a null pointer exception because the implementation expects non-null |
…micLink firebase-android-sdk requires a `@NonNull` Intent argument to the `getDynamicLink(Intent)` call, despite the documentation indicating otherwise Related firebase/firebase-android-sdk#2336 Related invertase/react-native-firebase#5662
#2629 is merged. Expect the fix to be rolled out in upcoming releases. So closing this issue now. |
The documentation of
firebase-android-sdk/firebase-dynamic-links/src/main/java/com/google/firebase/dynamiclinks/FirebaseDynamicLinks.java
Line 102 in 6ccc9de
states, that the intent parameter
However the parameter is annotated with
@NonNull
. So either the documentation or the annotation is wrong and needs adaptation.The text was updated successfully, but these errors were encountered: