Package name error in app engine connected android project after endpoint library generation

2
votes

After creating a new app engine connected android project it immediately generates errors in the build path of the generated client libraries. It suddenly happened in my other main project (that project has been working for quite some time) and after failing to solve it I created a new test project which has the same error from the start. I have tried cleaning the project, restarting Eclipse, even re-installing Eclipse... Any ideas?

Regards

See screenshots here:


(source: osmoel.se)

And


(source: osmoel.se)

2
androideclipsegoogle-app-enginegoogle-cloud-endpoints
I'm having exactly the same problem. I've now upgraded to GAE SDK 1.7.7.1, regenerated client libraries, and rebuilt everything, to no avail. I take it that, for you, the problem just went away? - Tom
Seems like an Eclipse bug to me (I'm on 4.2.2) as the error msg makes no sense (the declared package DOES match the expected package. When I try the 'quick fix' Eclipse does strange things confirming that it is very confused. - Tom
Haha - Yes. Eclipse was oddly confused. I waited a few days and google seemed to work out the problem. Sorry for the late response. - user2275151

2 Answers

1
votes

It seems that Google has some issues with Cloudendpoints today after the release of the appengine sdk 1.7.7. There was another problem described here where cloudendpoint users could not see their APIS in the api-explorer (https://developers.google.com/apis-explorer/)