Currently if the SDK believes the session to be unattributed, but the server is able to attribute the session and respond with a deep_link, the SDK will not update the session attribute and as a consequence not handle the deep_link.
This should be fixed so that if the session is currently unattributed, but the server responds with a deep_link, the session should become attributed. The session should determine how it is attributed in the same manner as though it resolved a short link. To be clear, that is the returned deep_link may contain a teak_rewardlink_id or a teak_notif_id, and the session should be attributed to a Link or a Notification accordingly.
Currently if the SDK believes the session to be unattributed, but the server is able to attribute the session and respond with a deep_link, the SDK will not update the session attribute and as a consequence not handle the deep_link.
This should be fixed so that if the session is currently unattributed, but the server responds with a deep_link, the session should become attributed. The session should determine how it is attributed in the same manner as though it resolved a short link. To be clear, that is the returned deep_link may contain a teak_rewardlink_id or a teak_notif_id, and the session should be attributed to a Link or a Notification accordingly.