I have a mobile App that displays YouTube videos in an iFrame that has worked perfectly for a number of years. A few months ago I started receiving reports that users are getting a YouTube '153' error and the video will not play. A Google search reveals many other developers having similar problems and a suggested work-around was to replace 'youtube.com' with 'youtube-nocookie.com' in the URL and to add the referrerpolicy="strict-origin-when-cross-origin" attribute. I've implemented both of these and still have the same problem.
I've been monitoring a number of threads on Google's issue tracker since the error began to appear a few months ago and their standard response is as follows:
Status: Won't Fix (Intended Behavior)
The reason you're seeing a 153 error is because you need to make sure and set your app ID correctly. If the referr is incorrectly set, that results to 153 errors.
Please update your web and mobile apps per our latest policy change described here: https://developers.google.com/youtube/terms/required-minimum-functionality#embedded-player-api-client-identity
Unfortunately I'm not sure how to use Construct to implement the client identity requirement described in their link. I've already set the App ID in Construct's Project properties field (using a 'reverse-DNS format'). Do I need to do anything else in order for this ID to be passed to YouTube?
Thanks,
Steve.