Scheme deep link returned as myapp://path treating path as host

[MauriMiguez]

Description

When Adjust uses "Scheme" deep links the path is interpreted as the host of the Uri.

A typical Adjust deep link looks like:

https://myapp.go.link/path?adj_t=...

However, after tapping the link the app may receive (if only scheme deep links is configured):

myapp://path

When parsing the URI: myapp://path, the path part becomes the host (i.e. uri.host == "path" and uri.path is empty). This means the app does not receive /path as a path segment, so it can’t route properly.

Steps to reproduce

1. Configure Android/iOS for scheme-only handling (scheme=myapp)
2. Create/use an Adjust deep link like https://myapp.go.link/path?adj_t=....
3. Tap the link on an device.
4. Observe the deep link received by the app after Adjust resolution.

Actual result

The app receives myapp://path, so interprets:

• host = "path"

• path = ""

Expected result

The deep link should be returned in a format where /path is actually a path.

[renancaraujo]

To fix this, adjust has to follow the URI spec RFC 3986 which states that "hostless" URIs should not contain the "authority" section (the // after the scheme).

So, myapp://path should, instead, be myapp:path. This way Uri.parse would interpret the dl propeely.