On Initializing branch from notification, callback not received in BranchUniversalReferralInitListener

[Discovery-Prachi]

Hello,

We have a use case, where we are using third party library for notification clicks. On Clicking notification third party library launches transparent activity, where Branch auto-initialises its instance. This transparent activity opens the main launcher activity and finishes.

When actual launcher activity opens, we are initializing the branch, we get following logs in the data, but don't get callback in BranchUniversalReferralInitListener.

returned {"session_id":"879713624464755900","identity_id":"879677955944158209","link":"https://dplus.test-app.link?%24identity_id=879677955944158209","data":"{"$og_title":"Jewels Of The Natural World","$publicly_indexable":"true","~creation_source":2,"$og_description":"A nature series that puts the focus on wildlife and various animals.","+click_timestamp":1610978298,"source":"android","$identity_id":836913166407675137,"$og_image_url":"https://ap2-prod-images.disco-api.com/2020/03/04/cfac4fb2-086b-459c-b248-2d4fc81713a2.jpeg?w=1080","~feature":"share_android","+match_guaranteed":true,"~tags":["5842_0"],"$desktop_url":"https://www.discoveryplus.in/show/jewels-of-the-natural-world","$canonical_identifier":"/show/jewels-of-the-natural-world","+clicked_branch_link":true,"$one_time_use":false,"~id":836926640361753083,"~campaign":"Jewels Of The Natural World","$canonical_url":"https://www.discoveryplus.in/show/jewels-of-the-natural-world","+is_first_session":false,"~referring_link":"https://dplus.test-app.link/HNU62ZoiZ9","~channel":"native"}","device_fingerprint_id":"878601838416932390"}

Because of this, deeplink is not navigated. Can you please help in debug. Logs image attached , after clicking on notification.

BlueshiftEventsNotificationActivity is the third party library activity (where auto-intialisation happens) which opens DPlusMainActivity (where callback is intended to receive)

[jf-branch]

Hey @Discovery-Prachi,

Wanted to follow up and see if you were able to resolve this issue, if not, we can investigate further.