[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, The reason you might see a 4xx on a request is best explained by checking whether an endpoints method actually exists on that path, whether your request had authorization, whether the request payload was malformed, or whether the correct request method (POST / GET) was used. The spe

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hi Nick, Thanks! I have completed the migration, including the stuff needed so I can see fancy graphs in https://console.cloud.google.com/endpoints. Some feedback: * The Errors graph is showing some 4xx, but drilling down just gives me log in json, and it doesn't show what the error is.

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, Just an update, in the Public Issue Tracker thread , we appear to have found another workaround as well. Cheers, Nick Cloud Platform Community Support On Friday, October 28, 2016 at 10:30:26 AM UTC-4, Nick (Cloud Pl

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, Thanks for your persistent reporting here. I've now managed to reproduce the behaviour and I've made a Public Issue Tracker thread to follow this for anybody along with you who is also interested in its progress.

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hi Nick, > Could you try to add the same @ApiClass annotation that you have on ApiV2.java to ApiV2Public.java and see if that prevents the error message? Yes, making the annotations identical in both classes prevents the error message. But, it means both must be authenticated, which defeats my

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, Could you try to add the same @ApiClass annotation that you have on ApiV2.java to ApiV2Public.java and see if that prevents the error message? I'm unable to replicate the issue using your code and keeping all the API names in web.xml, even regardless of whether I add the @ApiClass

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hi Nick, I've been using API Explorer (built-in tool from Cloud Endpoints), which does not require client library. Or should I use other tools? Regards, Thomas Wiradikusuma On Friday, October 7, 2016 at 5:54:50 AM UTC+8, Nick (Cloud Platform Support) wrote: > > Hey Thomas, > > Thanks for uploa

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, Thanks for uploading. I'll be sure to take a look at this project and see if I can manage to deploy it. However, in the mean time, I think there's a possible solution on your end that hasn't been investigated so far, as far as I can tell. The issue appears to me to be caused by comp

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, The issue wouldn't be that generation would fail - the idea is that due to having recompiled the API against different classes for V2, the old client might not be sending requests in the way expected. Could you try to load the updated client library into a client machine and see if

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hi Nick, The web.xml snippet I gave earlier is the one before I take one out: com.bla.ApiV2,com.bla.ApiV2Public Notice class ApiV2 and ApiV2Public. Also, I'm testing this from API explorer, which I think doesn't require the generation of client libraries. But, for curiosity sake, I did try it

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, Could you show what the web.xml file looks like before you take one out? I'm not sure how you've included both of them and it appears you uploaded a section from web.xml with only one Api class present. Also, just for testing's sake, have you managed to check whether recompiling th

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hi Nick, The error happens when receiving requests. I don't think it's necessary to update the client, as the update doesn't change the server. I'm posting here since I think it's either a bug of, or lack of documentation for, the V2 implementation @ApiClass. Let me explain. I have 2 classes t

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

Hey Thomas, This is just a guess, but it could be that it's necessary to update the client as well. Does that error occur when you deploy, or when you receive a request? That would be the way to determine if the issue is in the client needing to be updated or another issue (not clarified as yet