Description of issue: We have an HTML page which successfully passed the twitter validator tests. It contains the proper twitter player tags which link to our player and file media in question. When posted as a tweet, the twitter card/media shows up properly in line from the browser and also plays as expected. However, when the same tweet is viewed from a mobile device, it is displayed as simply a URL link and cannot be played from a mobile device. Are we missing something? The assumption was that the experience would be the same from either the browser or a mobile device…? Screenshots attached…
Adding more context based on recent discoveries:
From the mobile device, clicking the link listed above in the tweet causes an attempt to load the html page from the twitter app browser. A blank page is shown, however. This being despite the card playing correctly from the Safari or Chrome PC browser.
Grabbing the player URL which is specified within the twitter player tag and posting the player URL instead as a tweet results in different behavior. In this case, a URL is shown within the tweet both from the browser and mobile devices. Clicking the link from Chrome or Safari causes twitter to redirect to a separate browser page and allows the content to be played. Clicking the link from a mobile device also results in the target content of the player URL to play within the mobile devices/ twitter browser without issue.
URL affected (must be public): https://app23893550.heroku.cloudant.com/drumm_pages_test/f2657d5ab88cab575d6e1eafd8cda27c/DrummAudioPage.html
Troubleshooting steps attempted [note that we will not prioritise posts unless there is evidence of following the troubleshooting guides]:
We’ve culled through documentation and also followed troubleshooting guides. The only guess would be, despite being whitelisted, the card must also go through the approval process? Not sure.
From the browser:
From mobile device: