Post-it Code

About a month ago, we noticed that embedding YouTube videos in our mobile app (iOS & Android) started returning Error 15 or Error 153 . These embeds had been working for years with no code changes on our side. We discovered that many other developers were seeing the same error, especially in webviews inside apps, so the timing was curious. The likely cause It appears that YouTube’s embed policy enforcement has tightened: if the embed request originates from an app or webview that does not supply a valid Referer or Origin , YouTube may refuse to play the video (hence the 15/153 error codes). This meshes with policy guidance in the YouTube “Required Minimum Functionality” documentation, which states that apps must provide certain identifying information including origin. Source:  Google for Developers Additionally, many mobile WebView implementations (on iOS & Android) often send an empty or missing referer header by default, which then leads to this embed rejection. Ou...

Have you ever tapped on a URL link only to have it open an app instead of a website? This is known as deep linking. I hope the following note can help you in gaining greater understanding. Basic Deep Linking Deep linking allows apps to open specific content or trigger particular functionality within the app, based on a URL. There are two primary methods for deep linking in iOS and Android apps: Custom URL Scheme Universal Links (iOS) or App Links (Android) Custom URL Scheme   Both iOS and Android support custom URL schemes (e.g., myapp:// ) that allow apps to be opened directly via a unique URL. However, since these schemes can be defined without any centralized validation, there’s a risk that triggering a URL might unintentionally open a different app that uses the same scheme. Due to this security risk and lack of control, Custom URL Schemes are generally not recommended. Universal Links (iOS) or App Links (Android) Introduced after Custom URL Schemes, Universal Links (on iOS) an...