No response while creating short dynamic link if Google Play Services are present but disabled
See original GitHub issue[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:
- For general technical questions, post a question on StackOverflow with the firebase tag.
- For general Firebase discussion, use the firebase-talk google group.
- For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.
[REQUIRED] Step 2: Describe your environment
- Android Studio version: 4.2
- Firebase Component: Dynamic Links
- Component version: com.google.firebase:firebase-dynamic-links:19.1.1
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
After I try to shorten dynamic link there is no response from Firebase API regardless of callback
The code provided in section “Relevant code” will never emit if Google Play Services are present on the device but were manually stopped and disabled through settings. Note that this code works fine if Google Play Services are present and enabled. It works fine if there are no Google Play Services on the device through .addOnFailureListener { } However if Google Play Services happen to be disabled Firebase API fails.
Note that other callback such as addOnCompleteListener or addOnCancelled do not work as well. I can provide any additional info if needed. This is easy to reproduce and should be easy to fix. Thanks
Relevant Code:
Single.create { emitter -> Firebase.dynamicLinks.shortLinkAsync(ShortDynamicLink.Suffix.SHORT) { longLink = dynamicLink } .addOnSuccessListener { emitter.onSuccess(it.shortLink.toString()) } .addOnFailureListener { emitter.onSuccess(dynamicLink.toString()) } }
// TODO(you): code here to reproduce the problem
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top GitHub Comments
The team working on this has investigated the bug and it looks like the plan is to return an error immediately if this happens on Android TV. I don’t have a time frame on when this will be fixed, though.
@gsakakihara fyi