google-cloud-endpoints

GoogleAuthException: Unknown when authenticating with Cloud Endpoints

我与影子孤独终老i 提交于 2019-12-03 07:17:17
I'm trying to add authentication to my Cloud Endpoints, but I can't get it to work. I'm using this blog as a guideline: http://devthots.blogspot.nl/2012/07/building-awesome-android-apps-with.html What I have: In the AppEngine project: @Api(name = "noteendpoint", clientIds = { "123456789012-abcdefghijklmnopqrstuvwxyz012345.apps.googleusercontent.com" }, audiences = { "my_project_id.appspot.com" }, namespace = @ApiNamespace(ownerDomain = "example.com", ownerName = "example.com", packagePath = "myapp")) public class NoteEndpoint { // Rest of class, added parameter User to all methods. } In my

Versioning with endpoint V2 on GAE

杀马特。学长 韩版系。学妹 提交于 2019-12-03 04:01:19
I have the live version of my app deployed with its endpoints (no problem with that). I also want to easily be able to test other versions (e.g. staging). With endpointV1 : no problem. With endpointV2 : Everything works fine if I deploy to the live version (at https://[PROJECT-ID].appspot.com but does not work for other versions. After deploying to staging at https://staging-dot-[PROJECT-ID].appspot.com the deployment is successful, but when the frontend calls the backend, the request is received by the backend (I can see it in the GAE logs and trace list), but it does not make it to or though

Consuming GAE Endpoints with a Python client

北城余情 提交于 2019-12-03 03:53:10
I am using Google AppEngine Endpoints to build a web API. I will consume it with a client written in Python. I know that scripts are provided to generate Android and iOS client API, but it doesn't seem that there is anything comparable for Python. It does seem redundant to code everything again. For instance, the messages definition which are basically the same. It there anyway of getting this done more easily? Thanks You can use the Google APIs Client Library for Python which is compatible with endpoints. Normally you would build a client using service = build(api, version, http=http) for

Objectify loads object behind Ref<?> even when @Load is not specified

心已入冬 提交于 2019-12-03 03:41:20
I have an account object which references a user object. @Cache @Entity public final class Account { @Id Long id; @Index private Ref<User> user; public Long getId() { return id; } public void setId(Long id) { this.id = id; } public User getUser() { return user.get(); } public void setUser(User user) { this.user = Ref.create(user); } } I have hidden the Ref as recommended here: http://code.google.com/p/objectify-appengine/wiki/Entities - please note the Ref does not have the @Load annotation. When I call my Google Cloud Endpoint from an Android client, it looks like Objectify delivers the

Cannot import google cloud endpoints client library class in Android project

萝らか妹 提交于 2019-12-03 03:11:00
I'm having difficulty getting Google Cloud Endpoints working. I have an Python endpoints project running on GAE and it works perfectly using the api explorer. However I'm struggling to properly generate the client library and use it in my android app. I've tried a number of sample projects and have the same problem every time; I can't import and use the model classes from the client libraries. Here's what I'm doing (for this example I'll use the helloworld api python sample at https://github.com/GoogleCloudPlatform/appengine-endpoints-helloendpoints-python ) Unzip the sample code Generate the

GWT and Google Cloud Endpoints

假装没事ソ 提交于 2019-12-03 02:11:32
问题 A few days ago I've started developing a Backend for Mobile Applications using Google App Engine and Google Cloud Endpoints. This tutorial shows how the endpoints are getting generated automatically, as well as the client library for Android. So we have our Entity: @Entity public class Person implements IsSerializable{ @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Key key; private String name; //... } And the endpoint for this class: @Api(name = "personendpoint") public

Google Cloud Endpoints - Making calls with JS client, passing params and JSON body

点点圈 提交于 2019-12-03 00:33:15
I am having some trouble understanding some documentation on this. Located at ... https://developers.google.com/appengine/docs/java/endpoints/consume_js specifically ... // Insert a score gapi.client.tictactoe.scores.insert({'outcome': 'WON'}).execute(function(resp) { console.log(resp); }); // Get the list of previous scores gapi.client.tictactoe.scores.list().execute(function(resp) { console.log(resp); }); Seems like they are passing a score object, as JSON in the request body, to their API call for adding a score. Okay, sounds cool. It's unclear though on how you would pass a query parameter

Google App Engine vs Firebase

巧了我就是萌 提交于 2019-12-03 00:16:41
问题 I am trying to decide which option to go with. (or another if it is better) This is for a messaging type app where there will be high volume of notifications and database writes. Option 1 - Google App Engine using Cloud Endpoints and Cloud Datastore Pros: Able to build out an API the way I would like. Scalable Cons: More work implementing a notification system. (Which will end up being Firebase Cloud Messaging) Option 2 - Firebase Pros: Able to use the Firebase Database, Firebase User

Deploy cloud endpoints on custom domain

大憨熊 提交于 2019-12-02 23:57:40
I'm testing with Google Cloud Endpoints on App Engine and I've mapped my app to a custom domain. It appears that this is not possible. I've tried accessing the endpoint url, changing the host but this gives me a 404. I've also tried to change the root url and backend url for the service, but then I get this error after deployment: Endpoints: https://test.neenbedankt.com/_ah/api/myapi@v1 Error: API root https://test.neenbedankt.com/_ah/api not allowed on host version.myappid.appspot.com Can somebody confirm this is a limitation? For my current project this would be a showstopper. Correct, you

How do I test Cloud Endpoints with Oauth on devserver

半世苍凉 提交于 2019-12-02 23:24:54
My app uses Oauthed Cloud Endpoints and is working fine in production. My problem is that on the local devserver, my User user is always set to example@example.com , even though I've gone through the usual auth, access code, etc etc etc and have a valid authed user. I get that example@example.com is useful to test oauth endpoints before I have oauth working properly, but since my app is working I'd rather see the actual user there. To be specific, my endpoint method is @ApiMethod(name = "insertEmp"), etc public Emp insertEmp(User user, Emp emp) { System.out.println(user.getEmail()); // (A) log