I have had the dictionary app for almost a year. Never had a problem until today. When I press the speaker button to hear pronunciation I get a screen saying this:
Can someone please tell me how to solve it? I have tried battery pull and re-installing but nothing worked.
I sent an e-mail to their tech support, but the last time I contacted them about something they never replied. So, I don't know how optimistic to be about getting a reply this time.
Maybe if everyone with this problem contacts them? (The tech support e-mail address is on the app's page on BlackBerry App World.)
glad to hear I am not the only one. Anyone else has this issue? Any fix to this? Thanks again.
You are not alone. I have experienced this since yesterday on my 9700/.593. No fix or response yet from Dictionary.com. Gotta be something on their (server) side. Hope it gets fixed soon, because I use the app a lot.
That's really peculiar. I suppose I just got lucky. One thing I forgot to mention was that after deleting, resetting and reinstalling, I went into permissions and set all to allow, but you've likely done that too. Did either of you install anything new before the app started acting up?
PS - sorry for missing that in the initial post. Now have coffee!
So I just tried it again and I'm getting the same error. Like I said earlier, it happened to me a couple of weeks ago and reinstalling seemed to fix it. However, given what you guys are experiencing, it seems now like my reinstall just coincided with something external that initially resolved the error. Hopefully the app support people will resolve this soon.
Its a frustrating bug, but it really doesn't make much of a difference for me. I never used it. I just tried it on a whim and noticed that it didn't work.
Posted from my CrackBerry at wapforums.crackberry.com
I also have not received any response to my e-mail sent to Dictionary.com customer support last weekend. It's disappointing that such a widespread experienced error hasn't been addressed yet. And, to not even have a stock response to e-mail inquiries, well that's also disappointing...
And, to not even have a stock response to e-mail inquiries, well that's also disappointing...
That's what I say...
I also sent them a DM 2 days ago on Twitter with a Bit.ly link to this thread. I hope that gets them in gear, since it is not just one person. #Fail.
I'd like to know what was done to fix the problem. But, regardless, I'm happy to have the feature working once more.
Thanks for the heads up! Good info. After I saw your post, I now see it's working for me too....
As I stated before, it was obviously a server side issue, with no app update needed; however, I still have reservations & concerns as to why no one could provide any courtesy reply emails. Just because they can identify the problem, and will get it fixed in a relatively short amount of time, does not mean that they should leave adopters in limbo. I suspect because it's free, they don't really care. Anyway, I'm happy to have it back.
I want to bump this thread because I got this error every time I search for a word today. Had nothing to do with pronunciation, simply searching for a word gave me this error. Which closed down the app upon clicking OK. Its also worthy to note that I received another error just before this one at times that said connection could not be established or something along those lines. Even though as soon as I pressed enter, the word's definition came up, so the app WAS online, it just gave that error before the one shown in the first post of this thread.
Anything similar with other users?
It seems to be working fine now mind you. But it happened about 20 times (the number of times I tried using the app essentially) before giving up.
And what's up with their customer support? Do they even exist? Not a whisper from them.
Posted from my CrackBerry at wapforums.crackberry.com
