Audible Air error on HTC TP2 WM65

srabe01 · #1 (**permalink**) 08-04-2010, 11:55 AM

I have a Sprint HTC TP2 running WM65. Recently my Audible Air app throwing error when attempting to refresh my book list. It says: Error processing request SOAP-ENV: Client "No deserializer found to deserialize a ':UserId' using encoding style 'nul'."

Any ideas?

CoryNat · #2 (**permalink**) 08-04-2010, 02:28 PM

This happened after they did some upgrade to their servers. Kinoma cannot list books anymore either. Sent something to Audible Cust support and got this back. Still does not work though. Going to ping them back again:

On behalf of Audible I apologize for the inconvenience. With our recent updates there have been some issues that we are aware of and are working diligently to resolve. This also includes issues with Audible Air being down and is the reason you are receiving the error message you have. We are hopeful this will all be resolved very soon, try Audible Air tomorrow and everything should be back to normal, if not you can contact customer service or reply to this email for further assistance. In the meantime you will be able to download the title to your computer and transfer to your device. Feel free to contact us with any questions you may have.

For additional questions, how to contact us and hours of operation, please visit us at: www.audible.com/contactus

Sincerely,

Audible Customer Support

srabe01 · #3 (**permalink**) 08-04-2010, 02:53 PM

Thank you very much, CoryNat. I'll give it a few days and try again.
Scott

CoryNat · #4 (**permalink**) 08-04-2010, 07:23 PM

No prob. If I hear anything positive back, I will let you know.

kyderr · #5 (**permalink**) 08-12-2010, 09:51 AM

I too am suffering this. I am going to audible now to check it out. Still happening today.

Existentialism · #6 (**permalink**) 08-12-2010, 12:38 PM

Yeah, it's still happening for me too. They better fix this soon. Grrr.

CoryNat · #7 (**permalink**) 08-12-2010, 01:18 PM

Heard from them again on Tues. They say they are still working on it.

kyderr · #8 (**permalink**) 08-12-2010, 01:21 PM

What could they possibly have screwed up that takes seven days to fix? On a production server? That deals directly with revenue?

Existentialism · #9 (**permalink**) 08-12-2010, 01:27 PM

I honestly think they don't care. They've likely given up on WM. I'd bet a million dollars it's not affecting Android or iPhone.

CoryNat · #10 (**permalink**) 08-12-2010, 03:06 PM

I think you are exactly right. I have more hope of Kinoma figuring out the problem and fixing their software first than audible.