A bug in custom domain / HR datastore app management.

[Sergey Schetinin]

TLDR: There's a bug in Google Apps / App Engine that make it impossible for me to manage an existing domain alias.

I have an application that uses HR datastore, the app has an alias on a custom domain. The problem is, I can't manage it. When I log into Google Apps dashboard and navigate to Settings -> Services, the app is listed on the left, but I get an error trying to access the management page for it: "We are unable to process your request at this time. Please try again later. (Error #1000)", but management pages for every other app with an alias on that domain work fine.

If I start with the appengine dashboard and go Application Settings -> Domain Setup -> Add domain and enter the domain where it's aliased, I do get to the management page, but it lacks the existing alias, so I can't remove it. In the Apps dashboard, this app is now listed twice -- once with the s~ prefix, and not working, and once without a prefix, but lacking the existing alias.

I suppose the reason for this is that the app and the alias were created quite early after the HR datastore was made available, and the s~ hack was handled differently then and now.

I suppose I need to provide Google with the App Id and the domain name, but please contact me off-list for those.

Thank you.

-Sergey

[Sergey Schetinin]

The problem is still there. Can I please get a reply from a Google employee?

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/D_CllGMhIi8J.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

--
http://self.maluke.com/

[Sergey Schetinin]

While I was contacted by Greg off-list (thanks), the issue is still
there, after almost two months. It exhibits itself slightly
differently, but is still not fixed.

Now not a single appengine app can be removed from the Google Apps
account. Can please a Google employee reply and I'll provide exact
steps to reproduce.

--
http://self.maluke.com/

[Robert Kluin]

File a production issue.

[Sergey Schetinin]

The issue I talked about with Greg was bounced to the Apps team
anyway, as it's not appengine's fault.

Trying to file production issue resulted in "400. That’s an error.
Your client has issued a malformed or illegal request. That’s all we
know." which is not nice, let's put it that way.

In the end persistence paid off and the production issue was filed:
http://code.google.com/p/googleappengine/issues/detail?id=5617

All of this is quite sad, really. I'm not even asking for help, I'm
reporting what's broken with Google's service, why do I have to work
so hard to get it noticed?

--
http://self.maluke.com/

[Gregory D'alesandre]

Hi Sergey, we've definitely noticed and appreciate you reporting the bug to us!  The bug notes a workaround now and we are working on more permanent fixes, unfortunately those fixes often take times both to implement and then to deploy.

Greg

[Sergey Schetinin]

Yeah, thanks for suggesting the workaround. I understand that there's
a lot happening with App Engine, so it's impossible to respond to
everything, but reporting problems with GAE is usually a very
frustrating experience (and I don't think it's just me).

[Gregory D'alesandre]

Thanks for the feedback Sergey and I don't think its just you either.  We are working to make the process less frustrating and ensure everyone understands that we do actually read bug reports and work to resolve them :)

Greg