“The workaround is to place the wearable APK in the res/raw directory instead,” according to Google. In other words, as highlighted by the four steps necessary for the workaround to take effect, this is not something that should be done by the technically unsound among us. For those unfamiliar with HTML, it might be a good idea to simply wait for an update.
The problem lies in Google’s app encryption measures. These measures, meant to dissuade pirating, encode paid apps with a device-specific key. Unfortunately, the bug prevents the system from properly extracting the Android application package (APK). Because of this, the installer assumes there is nothing to install and aborts the process.
There is no word from Google on when it will issue an update to rectify the situation, but it would be a good idea to keep an eye out for one in the near future.
