I am using this link to build a simple chat application using GCM, and I found this great feature "Google Cloud Endpoints" which makes things easier. But I am afraid to depend on it as I noticed it is still experimental. Can I trust it or should I use Java Servlets instead?
It is true that the tag 'experimental' is a bit scary. If you are concerned, you could consider holding back a bit until Google IO 2013, which is the middle of May. They often make announcement and introduce new technologies there.
They first announced endpoints at last years' Google IO (in July) and if there any significant changes pending for endoints they would likely announce them at this years'.
If you do start using Endpoints, just for Android, and w/o user authentication, I don't think it would be too hard to revert to using a Servlet instead, if you had to (i.e. due to a change in terms that was off-putting). The user authentication stuff would be harder to replace IMO.
As far as I have used Google Cloud Endpoints they work perfectly. Furthermore many interesting features are already implemented, such as integration with Google Eclipse Plugin and testing through the Google APIs Explorer, even in localhost, using the Development Server.
I understand they're still experimental maybe because they're just a new technology not really thoroughly tested yet and are subject to updates. Anyway I've not found significant bugs so far and you should be able to reuse your endpoints with the sucesive versions that will exist. It doesn't seem to be something that will dissapear in the near future...
This is an older question, but for further references I want to say that my short experience was not so pleasant.
I tried "Mobile Backend App". In the beginning, everything worked fine, but after a few days (without changing anything) I received:
GoogleJsonResponseException 404 Not Found
I sow other posts on stackoverflow and manage to solve it by creating another project. I changed the code and it still worked. But again I had problems I played a bit with the 2 projects, I redeployed and changed the settings (tips found on other posts) and it worked. Now it is no longer working, no matter what I do.
I hope that the problem is specific to this project, but nevertheless it is frustrating.
Related
One of our PHP GAE apps stopped working today, because the path that GAE serves our app from changed from /srv/ to /workspace/. In an ideal world we wouldn’t have depended on that path, but… details.
Does anyone have further info on the change? Does GAE consider this an 'implementation detail'? It doesn’t seem to have reached all our instances yet, which will make managing the change a little painful, and I couldn't see it documented anywhere.
(Apologies, this doesn't really feel a great fit for StackExchange/Overflow, but Google says I should post any 'technical questions' here....).
Both instances are running appEngineRelease 1.9.71 weirdly.
When deploying using gcloud app deploy I get the following error:
Timed out waiting for the app infrastructure to become healthy gcp
I contacted GCP Support and they told me the same thing I had read in other threads:
the error you are referring to may be related to the Compute Engine “In-Use IP Addresses” Quota limit. You can view your current quota limit information by accessing from your GCP menu “IAM & Admin > Quotas”.
I checked the "In-Use IP Addresses" and it doesn't seem like I have a problem with quotas:
Looking for the error, I found that in the Activity tab, when deploying, I get an error. Apparently , when App Engine is trying to delete a VM, the process starts to loop trying to delete it. You can see the error:
(I intentionally covered the project ID)
Edit: It seem like the problem is only with southamerica-east1. I created a new project in southamerica-east1 but I kept getting the same error, so then I created a new project with the App Engine in us-west2 and worked like a charm (I used the same application and app.yaml). I wonder if the problem is GCP southamerica-east1 or a unknown bad configuration by my side.
This is probably related to this issue: https://issuetracker.google.com/u/2/issues/73583699. It does mentioned the "in-use IP Address" quota, but many people have posted in recent days (Nov 2018) indicating that they are seeing the error and have verified that they have not hit their quota.
Unfortunately, no solution has been posted and there hasn't been any recent comment from the devs.
First, our apologies that you’ve experienced this issue. Be assured that we are aware of the situation and the team works hard to resolve it.
Our goal is to make sure that there are available resources in all zones. This
type of issue is rare. When a situation like this occurs, or is about to
occur, our team is notified immediately and the issue is investigated.
We recommend deploying and balancing your workload across multiple zones or
regions to reduce the likelihood of an outage. Please review our documentation
which outlines how to build resilient and scalable architectures on Google
Cloud Platform.
For the time being, you can try relaxing your requirements (e.g. requesting a smaller instance or one with fewer resources) or removing the external IP requirement.
If that proves not to be enough, you can try deploying your application to another region
Again, we want to offer our sincerest apologies.
Thanks for understanding.
At the end we didn't find a real solution so we moved all our services from Brazil to US-2. I'm not sure if the Region is the problem, but there in US-2 all works like a charm
We know that OAUTH flow cannot be implemented in Office add-ins like you would do for a normal (non iFramed) web app, we must rely on some popup technique: see the best explanation here.
To overcome this, Microsoft released a dialogAPI within Office.js. This dialog API for a while was only available for Office Desktop.
If a developer wants to have a solution that works on Office Online (and to be allowed to be distributed on the Office store) he had to implement a fallback solution involving a plain old browser pop-up.
Remark: this is what we do in the open source sample for Outlook that we released.
As explained in the Documentation, to test the availability we have to check using this code sample
if (Office.context.requirements.isSetSupported('DialogAPI', 1.1))
{
// Use Office UI methods;
}
else
{
// Alternate path
}
The thing is, today, I tried to force the usage of dialogAPI even when the if() statement returns false. Surprise, it looks like dialogAPI is working even in Office Online ! (Chrome, Edge, FF, IE tested). That rocks!
My questions are:
Will we have dialogAPI in Office Online for all browsers (including mobiles)?
Can we have an ETA when this will be production ready?
Will we have to continue implementing a fallback solution?
What about old Office builds (if it works for all browser maybe for old IE as well)?
Yes the dialog API will be available for online hosts and it will work across all major modern browsers. As for the ETA I cannot give you a specific date but rest assured this is top of mind for us. You can check the official status in our Add-in Availability page; the API is already available in Windows Desktop, Mac, IPad.
Benoit, I will reach out to the team to see what the status is, and we'll try to get back to you.
In terms of general info: features do often get deployed "dark" -- and for example, in Excel APIs, which is the area I work on primarily, we might have ExcelApi 1.3 be something that we work on for several months... but it's not like we don't check in anything during that time! Rather, we continuously check in and roll changes to production, but we make no guarantees about them being available and/or fully tested until (Office.context.requirements.isSetSupported('ExcelApi', 1.3) returns true. So, you might well be seeing that most of the functionality is already in -- but the team hasn't fully "signed off" on this yet. So, I would consider this to be internal/non-production API until isSetSupported does return true; but you probably can infer that the feature is getting close to complete, and so it should be lighting up in the not-too-distant future (disclaimer, I personally have little visibility into this particular API; so take this with a grain of salt).
I assume that 0.6.2 is just an improvement on 0.6.0, but would like to make sure of that. If my app builds fine with 0.6.0, swapping in 0.6.2 shouldn't cause any compile errors, right?
We've been pretty fast-and-loose with the <1.0 versioning for the Watson Developer Cloud iOS SDK. The biggest changes between v0.6.0 and v0.6.2 relate to the Conversation service (here's the commit). We tried to only add to the API rather than change it, but might have made minor tweaks along the way that could result in changes to code that uses the Conversation service.
A client of mine has asked me to look into moving an app that's using Drools from AWS to Google App Engine. I've done a bit of research, and from some old postings on the net, there seemed to be some problems using Drools on GAE, due to the fact that it does file I/O which is not allowed.
Does anyone know if this has been addressed in a newer version of Drools? I've tried searching, but the only responses I get are fairly old (> 1 year)
As far as I know it will not work out-of-the-box with newest version, did you try it at least? If you have errors we can help you to solve them if we see at least a possibility to make it work.
Cheers