API code not working with Teamviewer 14

Since upgrading to Teamviewer 14, the links in our web based CRM system no longer work. You click on the link and rather than open Teamviewer with the ID of the device we want to connect to, it just tries to download teamveiwer.dmg (I'm on a mac). If I cancel the download and just enter the ID number of the device directly into the teamviewer page it has opened and click connect, again it just tries to download Teamviewer again.

I have uninstalled, reinstalled, tried installing with the file it downloads each time just in case it is different in some way but nothing works. If I go back to Teamviewer 13, the link works perfectly. Problem is that if I leave 13 on, every time I talk a new client through installing Teamviewer on their workstation, when I try to connect to them I keep getting asked to upgrade my Teamviewer.

Please can you tell me how I can resolve this? I called the Teamviewer support number yesterday but despite accessing my computer and having a look, they didn't know the answer.

I am using 14.0.13880. How can I make this work in 14 like it does in 13?

Thanks

Find more posts tagged with

Comments

DomLan

Hi @tatty27,

hope this help.

Regards

tatty27

How do I do that please?

DomLan

Maybe....

behind that link, a page is requested which, via javascript, provides to recall a protocol on your client. This corresponds to a call of the type "teamviewer10://control?Device=xxxxxxxxxx". If your device (mac) has a valid application to which to forward this request, then it is passed to the request. Otherwise the download of the last valid version starts.

Check your protocol association (teamviewer10:// -> start TeamViewer 14)

Regards.

tatty27

I'll try again...

I don't belive the code for the link in our CRM is incorrect.

If I got to this page

https://start.teamviewer.com/en/

And enter the ID I get the same problem, it tries to download a new copy of teamviewer.dmg to install, and this happens with chrome, safari and firefox.

$team_id = teamviewer id pulled from our database

<a href="https://start.teamviewer.com/<? echo $team_id; ?>" target="_blank" style="text-decoration:none;">
  <img src="img/team-viewer-icon.png" alt="Connect" title="Connect" border="0" width="30" />
</a>

The above code perfectly fine with Teamviewer 13. It's almost as if the start.teamviewer.com can't see the Teamviewer 14 on my mac even though it is up and running and I am using it every day. I have the same problem on my laptop which is a macbook pro.

I have tested it on a Windows PC with Teamviewer 14 and my link works fine so it is just macs that are affected.

Hope that helps?

DomLan

As the ancients did ...
Use a carriage return instead of a backslash: eg.

https://www.teamviewer.com

part01

part01

?soon=12345

I think I can do to rebuild the link ...

tatty27

Hi,

I replied and the teamviewer page deleted my reply saying it was spam

How do I write links without that happening?

tatty27

Hi, This is my link...

$team_id = teamviewer id plulled from our database

<a href="https://start.teamviewer.com/<? echo $team_id; ?>" target="_blank" style="text-decoration:none;">
<img src="img/team-viewer-icon.png" alt="Connect" title="Connect" border="0" width="30" />
</a>

I have tried this by using the literal teamviewer ID rather than pulling it from the database and it still doesn't work. The above code still works perfectly with Teamviewer 13.

I have also tested by entering the ID number at this page

https://start.teamviewer.com/en/

And I get exactly the same problem, it tries to download teamviewer.dmg and install Teamviewer again. I have also tested with Chrome, Safari and Firefox and get the same issue.

This makes me think the problem isn't the way my link is written, it seems that the action instigated by the https://start.teamviewer.com/en/ can't see the Teamviewer 14 installed on my mac which is running macOS Mojave. I am also having the same problem on my Macbook Pro

Thanks.

DomLan

Hi @tatty27,

could you indicate which link you are composing on your CRM, concealing the unique references that concern you. In this way it would be possible at least try to replicate the hops making your request by examining the network traffic.

Regards

tatty27

Please?