Player card whitelisting rejected: "Your card doesn't load on any platform"


#1

Twitter player card rejected by email for the following reason:

Test your experience across all Twitter clients, including Twitter’s iPhone and Android apps, as well as twitter.com and mobile.twitter.com. Cards that do not work in all Twitter clients listed will not be approved. Your card doesn’t load on any platform. Please check your meta tags. Testing instructions are available here: https://dev.twitter.com/cards/types/player#Testing_your_Card

But I have tested the twitter:player url in all the supported clients (android and iOS devices) with no trouble according to twitter instructions in the url mentioned above.

According to the email they are unable to load the card on any platform so I can’t figure out what’s the problem. Any feedback on this would be greatly appreciated.

The card is audio only and specifies the twitter:player url only. One example of the card is shown in the following url https://hyhy.co/p/gLD.MT

The card validator output (which show the card correctly):
INFO: Page fetched successfully
INFO: 25 metatags were found
INFO: twitter:card = player tag found
WARN: Not whitelisted


#2

If the content is audio-only, that is likely to be the issue. The Player card is intended for video content.


#3

Thank you Andy for your response.

I’ve been reading the documentation and getting the idea that the player card is for audio or video, let me quote some text from the docs:

https://dev.twitter.com/cards/types/player :

Video clips and audio streams have a special place on the Twitter platform thanks to the Player Card.

https://dev.twitter.com/cards/overview :

Player Card: A Card to provide video/audio/media.

Besides, I’ve seen working solutions for audio only player cards in twitter, like this one (soundcloud):
Tweet Direct Link https://twitter.com/rsateler/status/537201059463036930

Are you 100% sure that audio only player cards are not allowed? why wouldn’t the support team from card validation mention this issue (twice)?


#4

You’re right that we do have specific audio cards but these are only for a limited number of domains at this time. The docs for the player card do indeed mention audio streams which is a little confusing (to me). I’ll have to check in with the platform team to see whether the reason your card was rejected was that it was audio only, that was a guess on my part without double-checking :blush:


#5

Hi @rsateler, I’ll talk to whoever reviewed your card so that I can provide more context. I doubt this rejection was due to a policy issue. Taking a glance at the card and taking into account the email you received, I would assume the problem is the extra white space in your player card on web. I would suggest changing your player dimensions to the following:

<meta name="twitter:player:height" content="590" />
<meta name="twitter:player:width" content="528" />

#6

Thank you @andypiper for double checking, that would be great.

Hi @jbulava, thank you for the response. As you can see the twitter:card url in the page that has the meta tags is different (https://heyheyapp.com/p/gLD.MT?twembed), and it is designed to fill the available width (as per twitter card docs instructions). Anyhow I will try again changing the size parameters that you suggest and let you know how it goes.


#7

@andypiper and @jbulava, the card is now whitelisted, it seems that it was approved now. Thanks a lot for your help!!

One question though, in every card shared you can see a reference at the top to my personal twitter account.
How could I change this to the company’s twitter account? Is there a twitter:id meta I don’t know about? Or it depends on who applies to white-listing (which I did using the company twitter account)? Thanks again for your help.


#8

Last week I manually whitelisted your card and noted your screenname as the default “site user.” I’ve updated it just now to @HeyHey_App. You can always overwrite this attribution by using the twitter:site meta tag.


#9

Thank you @jbulava, will use twitter:site meta tag from now on.
Best,


#10