google-cloud-endpoints

I made web app using GAE's Cloud Endpoints. App has only backend part. App calls Google Places API and parses JSON responses, creating objects which returns to client. Client is Android app which uses generated client libraries from GAE. My problem is folowing: app running on local dev server shows on Android correctly UTF-8 formatted strings, but deployed app is showing on Android messed up strings. E.g: Instead of Klinički Centar it shows Klini��ki Centar. I'm using latest Fedeora GNU/Linux, developing in Eclipse Kepler (newest edition), GAE is ver 1.8.1, Google Plugin for Eclipse ver 3.2.4

Google Plugin for Eclipse includes a facility to automatically generate the cloud endpoints client library. But there doesn't seem to be an easy way to move the generated source.jar file into your Android source. The documentation https://developers.google.com/appengine/docs/java/endpoints/consume_android says The Endpoints generation results in a sources jar file. Add the contents of this jar file to your Android project. It doesn't seem possible to put the source.jar file into an Android /lib or /libs, since the source is .java rather than .class form. So I just manually copy over the source

i've been following the tutorial in Creating an Endpoints Backend from an Android Project . Everything is compiling and looks promising. The backend is up, i changed CloudEndpointUtils#LOCAL_ANDROID_RUN to 'true'. but when i try to test the app on a real device (not emulator) im failing on - java.net.SocketException: failed to connect to /10.0.2.2 (port 8888) after 20000ms: isConnected failed: EHOSTUNREACH (No route to host) So i looked at CloudEndpointUtils and saw that setting LOCAL_ANDROID_RUN to 'true' makes the app look for DevAppServer in http://10.0.2.2:8888 , which is the emulator

I have been doing extensive research on how to authenticate your client (Android, iOS, web-app) with Cloud Endpoints without requiring your user to use their Google account login the way the documentation shows you. The reason for this is that I want to secure my API or "lock it down" to only my specified clients. Sometimes I will have an app that does not have a user login. I would hate to pester my user to now sign in just so my API is secure. Or other times, I just want to manage my own users like on a website and not use Google+, Facebook, or whatever else login authentication. To start,

Am I correct in thinking that the goodness of Cloud Endpoints comes with the following limitations: The REST Api cannot be deployed to a custom domain (it'll remain on appspot.com). The only authentication supported is OAuth against Google accounts. Corollary: it isn't currently possible to create a user login/session-tracking mechanism that is Google-accounts-agnostic (e.g., with email as username and a password). Is there any plan to do away with these limitations and if so, what is the ETA? Taking these item by item: Currently, yes this is still the case. Keep in mind, our initial release