It emerged earlier this week that paid Android apps leave the DRM encryption element behind when transferred to an Android Wear device via Bluetooth. Translate: paid content didn't work.
As a result, Google is promising a fix, but in the meantime has advised app developers to move the encryption files to a different portion of the app in order for the transfer to be successful.
In a post on the Android Developers' blog Google advised users to move the APK from the "assets" directory folder into the "res/raw" directory in order for paid apps to work.
Big fix on the way
Google has yet to release details of when it'll bring the full fix into place, but has promised it in a future update.
The blog post read: "We will be updating the 'wearApp' Gradle rule in a future update to the Android SDK build tools ... We're working to make this easier for you in the future, and we apologize for the inconvenience."
Via The Next Web
Get daily insight, inspiration and deals in your inbox
Get the hottest deals available in your inbox plus news, reviews, opinion, analysis and more from the TechRadar team.
A technology journalist, writer and videographer of many magazines and websites including T3, Gadget Magazine and TechRadar.com. He specializes in applications for smartphones, tablets and handheld devices, with bylines also at The Guardian, WIRED, Trusted Reviews and Wareable. Chris is also the podcast host for The Liverpool Way. As well as tech and football, Chris is a pop-punk fan and enjoys the art of wrasslin'.