Mike DiGiovanni Andy Lin : Jenny M from the Glass Developer Team replied to my question about your app, it's a start...
Mike DiGiovanni Andy Lin : Jenny M from the Glass Developer Team replied to my question about your app, it's a start at least:
https://www.glass-community.com/t5/Discussions/Goodbye-all-I-ll-no-longer-be-exploring/m-p/140104#M37357
https://www.glass-community.com/t5/Discussions/Goodbye-all-I-ll-no-longer-be-exploring/m-p/140104#M37357
https://www.glass-community.com/t5/Discussions/Goodbye-all-I-ll-no-longer-be-exploring/m-p/140104#M37357
https://www.glass-community.com/t5/Discussions/Goodbye-all-I-ll-no-longer-be-exploring/m-p/140104#M37357
Hey Serge,
ReplyDeleteFrom looking at the code, I don't see any big issues with getting this to work with XE16+. Mike just needs to update this app
We did indeed make some beraking API changes from XE12 to XE16, but we told you all ahead of time that they'd be coming. It was part of the sneak peak: feel free to hack around, but stuff is going to break with each release. With XE16 we graduated GDK to developer preview, kind of like a beta. We're not making surprise breaking changes any more, so stuff should be a bit more stable.
All that being said, there is one part of this app that may be an issue going forward. It uses Android Debug Bridge as a work-around for security features. By default Android does not let apps control your devices because it could cause a whole bunch of yucky security issues. ADB is a useful development tool, but it is not a stable API. It didn't change much between XE12 and XE16, but it could change at any time in the future without warning.
Interesting. As far as I could tell ADB did change, it looked ljke the kit Kat jump made it so you couldn't authorize the local device . I'll take another look since we've been through like a dozen releases since then.
ReplyDeleteSerge Berig good stuff. Thanks for asking her.
ReplyDeletefeel free to jump in the thread and tag her/ask more
ReplyDelete