Old Deeplink behavior

[rbaldonado]

With the new Deeplink address (https://webxr.run/…), is there anyway to make deeplink behave they way they did before?

For instance in the example below, the project uses Z.device.launchUrl(“zappar://z/65xk1c”), and opens the new project seamlessly in Zappar.

Support for Multiple Targets

Hi guys, Just thought I’d mention a few things regarding multiple-image tracking in Studio. While creating an experience that tracks from several targets is possible (as is evident from some experiences we’ve seen, including @stevesanerd’s competition entry), it is not currently supported nor recommended due to the instability and unreliability of the implementation in its current state. Support for multi-image tracking has been discussed internally, but as it’s part of a much larger discussi…

But the new deeplink address forces the zappar app to open a browser in itself then, then ask the user to launch zappar.

Can I get the old deeplink code back?

[rbaldonado]

Answering my own question: Yes. read this article How to get a Deep Link ID