Google Offers Temporary Solution for Android Wear Bug

Encryption issues have been a bane for Android developers attempting to sync paid apps with smartwatches. Without the proper documentation in place, Google is still playing catch up. 

Android wearable apps are as of now downloaded and locally stored on an Android phone. From here they are transmitted via bluetooth to the smartwatch. According to Android Police, paid apps haven’t been opening due the key code incorrectly remaining encrypted, causing the app to not install or open at all.  

Google’s solution recommends that developers automate manually placing Android Wear APK in the “res/raw” directory instead of the “assets” directory to avoid encryption as the assets directory becomes locked. This is a temporary fix; many await more updates from Google in the near future to address documentation and bug issues with wearable devices. 

Original Article

Update: Google posts DRM workaround for paid Android Wear apps

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.