Different behavior opening a web intent link in mobile browser vs Twitter App

mobile

#1

(Note I only have an Android phone, so below comments apply to that. I’ve been told the issue is also present on iOS).

When using a web intent link on some pages of our site, we are getting a different set of behaviors when the link is shared by browser vs the Twitter App.

<a href="https://twitter.com/intent/tweet?url=http%3A%2F%2Fwww.bloomberg.com%2Fsponsor%2Fubs%2Ftogether%2F%3Fmvi%3D9425a299d5c44c5395ba372d21d8189c&amp;amp;text=Sponsor Content: How%20unconstrained%20asset%20allocation%20can%20lead%20to%20outperformance&amp;amp;via=business" class="bloomberg share link bb-social-link bb-social-link--twitter" target="_blank"></a>

For the above link, in browser it shares with the proper title, followed by the url and the @business tag. However, when this link opens in the twitter app, it only shares the url, with no title or via @business present.

From the documentation available here (https://dev.twitter.com/web/tweet-button/web-intent), it doesn’t look like anything is malformed, as we are using the text, url, and via parameters. Any help would be appreciated.

Thanks,
Spencer


#2

Is the &amp;amp; output in your query parameter output or just the HTML copy and pasted into this forum?

The entire text query parameter should be URL encoded.


#3

Looks like its just due to copy and paste into this forum. When clicking on the link in a browser, this is the url it goes to:

https://twitter.com/intent/tweet?url=http%3A%2F%2Fwww.bloomberg.com%2Fsponsor%2Fubs%2Ftogether%2F%3Fmvi%3D9425a299d5c44c5395ba372d21d8189c&text=Sponsor%20Content:%20How%20unconstrained%20asset%20allocation%20can%20lead%20to%20outperformance&via=business


#4

Wanted to follow up that this issue still occurs. As far as we can tell, the intent URL (above comment) is correctly formatted, yet causes problems when launching into the Twitter App on Android and iOS.


#5

Hi @niall! Thanks for your help so far. This is still an issue occurring on our mobile pages, as Spencer said. It’s preventing our users from sharing articles via their mobile devices, which is a pretty big deal for us. Is there anything else we can do to solve the issue?


#6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.