I've found an answer to one of the mysteries.
mGoogleApiClient = new Builder(this)
.addConnectionCallbacks(this)
.addApi(LocationServices.API)
//.addApi(Wearable.API) // used for data layer AP
.addOnConnectionFailedListener(this)
.build();
If you request the wearable api, it might say that the client is available,
yet fail trying to connect, asynchronously, with unknown error 16.
My local test devices all had the Android Wear app installed even though no
wearable has ever been paired with them. Presumably, many of the end user
devices, and the devices in my remote test lab, do not.
Probable solution is to use one client per API if some are optional.
Nathan
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
