Deferred deep link callback is not triggered in ios 17/18

[HungPVRikkei]

Currently, I am developing a new user feature. I have followed the steps as outlined in the documentation. However, while there are no issues on iPhone OS 15 or 16, when it comes to iPhone OS 17 or 18, I noticed during debugging that the adjustDeferredDeeplinkReceived function is not being called. I’m not sure if there’s a missing configuration, because if something were missing, it wouldn’t have worked on OS 15 or 16 either.
SDK Version:

• Adjust/AdjustWebBridge (5.0.2):
  • AdjustSignature (= 3.35.2)
• AdjustSignature (3.35.2)

[HungPVRikkei]

@uerceg can u help this case ?

[uerceg]

Hey @HungPVRikkei,

Can you redo your test with the SDK in sandbox environment and log level set to verbose, pick up all the logs and send them over? Feel free to omit data you might not want to share such as app token, event token(s) or anything else you might find sensitive.

[HungPVRikkei]

Dear @uerceg
Sorry, due to some confidential information, I cannot upload the log segment, but I checked on two devices. On the device running iOS 15.4.1, it works fine, and the log shows the segment "[Adjust]i: Open deep link (...)", while on the device running iOS 18, I don’t see it. Additionally, can you let me know if there’s any specific log segment you’d like me to check?

[uerceg]

You can find my email on my GitHub profile page. Feel free to send the logs from the iOS 18 device over there and I'll check what's up.

[HungPVRikkei]

Hi @uerceg
I have debugged and found that the error lies in the ADJAttributionHandler file, specifically in the code line attributionResponseData.deeplink = [NSURL URLWithString:deepLink];. Currently, I am using Xcode 16.1. With the same URL, on iOS 15/16, [NSURL URLWithString:deepLink]; always returns a value, but on iOS 17/18, it always returns nil. This is why the adjustDeferredDeeplinkReceived function is not being called. Here is the sample URL where I encountered this bug:

abc.net://?adj_t=9vj38fk4&adj_deep_link=appabcnet%3A%2F%2F%3Fcast_login_id%3D29468400%26intm%3DA0456ABVC732615721%26adcd%3Dos1019%26type%3D11&adjust_no_sdkclick=1

[uerceg]

Hey @HungPVRikkei,

Thanks for letting us know. We'll check this on our end and keep you posted.

[uerceg]

@HungPVRikkei So you are observing this issue while testing the deferred deep linking scenario? Can you send over just the log line which is indicating the attribution value the SDK got back from the backend? It looks something like this:

{"app_token":"qwerty123456","adid":"705eafe721452e914c00562b35905048","timestamp":"2025-03-03T07:59:55.417Z+0000","message":"Attribution found","attribution":{"tracker_token":"abc123","tracker_name":"Organic","network":"Organic","engagement_time":"0001-01-01T00:00:00Z","installed_at":"2025-01-28T21:31:14Z","first_session_time":"2025-01-28T21:31:14Z","is_reattributed":false},"control_params":{}}

Feel free to hide app_token and tracker_token values from it.

[dragongesa]

+1