Firebase Dynamic Link crashes. setResultOrApiException(Unknown Source:12)

[richardliveraise]

Firebase Dynamic Link crashes. setResultOrApiException(Unknown Source:12)

[ashwinraghav]

@richardliveraise Thanks for reaching out! We do anticipate that this would be fixed in the upcoming release schedule a couple of weeks down the line.
Thanks for working with us on this.

[richardliveraise]

@ashwinraghav can you clarify what root cause of this issue? any workaround I can do in the meantime? Thanks!

[richardliveraise]

@ashwinraghav I figured the issue was generating the short link. The workaround I did was generate a long link, then get the short link.

 //Generate long link
 Uri dynamicLinkUri = dynamicLink.getUri();
 return FirebaseDynamicLinks.getInstance().createDynamicLink()
        .setLongLink(dynamicLinkUri)
        .buildShortDynamicLink(); 

Reference:
https://stackoverflow.com/questions/52152116/short-dynamic-link-error-com-google-android-gms-common-api-apiexception-8/52157428#52157428

Note that prior doing the workaround, I updated the SDK to the latest one, then it'd work for newer OS (7.0, 8.0) but it wouldn't work for older OS (5.0, 6.0). If you could explain what the cause of this, I'd really appreciate it. Thanks!

[aguatno]

Hi @richardliveraise sorry for my late response here. It looks like the error log didn't persist in the latest version. I was wondering if you're still having this issue? If so, could you provide the following so that I can investigate the issue further:

• Minimal repro of your code that I can run locally
• Firebase SDK version you're using
• Any other relevant information

[google-oss-bot]

Hey @richardliveraise. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@richardliveraise if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.