question

I've tried the various "contact us" and "support" ticket systems, and I seem to only get the run-around from auto-responders, so I'm trying here. My next step will be to write a firey blog post, I guess. We have an app called "Nimble Storage 3D Demos" (53b0a12e553f40bba4cda0894b068e6e) (com.kaon.android.lepton.Nimble) that I submitted for review on Sept 29. It's been sitting "In Review" ever since (7.5 weeks). I thought maybe if I just pulled it and re-submitted, that might break the log-jam, but the "Cancel App Submission" button just gives me an error: [b]We are unable to cancel your submission for this application.[/b] When I submitted a ticket asking what the hold-up is, I got this canned response: [i]Thank you for writing in and sorry for the delay. We consider a variety of factors as we evaluate each app for Kindle Fire Tablets, including the quality of experience the app offers and compatibility with the device. While our goal is to offer a broad and compelling assortment to Kindle Fire Tablet customers, not all apps available through Amazon Apps are currently available on Kindle Fire Tablets.[/i] Which, of course, tells me nothing. I tried to follow up, and got this, probably also canned: [i]Thank you for writing back. We do not have any additional information at this time. We have noted your case number and app name, and if we do have additional information, we will reach out to you directly by reopening this case.[/i] So I let it sit for a while. No change. Thank goodness our customer doesn't really care about the Kindle, or we'd be getting a lot of heat right now. But we like to make our apps work everywhere, so I'm keeping up the fight. I've opened a new ticket, and got the same canned response I got the first time. So I just followed up, and I suppose I'll get the same canned second response to that. Has anyone here found the secret key to getting [b]actual[/b] developer relations support from Amazon? With Apple, for example, it's relatively easy to get an actual human being to take on your case and get whatever is going wrong fixed. But I can't find any mechanism within Amazon for that. So, like I said, if this post goes unanswered, I guess my next step is to write a scathing, hilarious blog post about the mess that is Amazon Developer Relations (oh, I have some [i]good[/i] stories to tell), and see if I can embarrass somebody into doing something about this.