Hi,
I keep getting notifications to update my password for the Twittly application, which was uninstalled from my device.
Any ideas? this is annoying
Thanks
Cvcv
Printable View
Hi,
I keep getting notifications to update my password for the Twittly application, which was uninstalled from my device.
Any ideas? this is annoying
Thanks
Cvcv
you restored after doing an OS leaked update, right?
load the OS again and don't restore. Only way to stop it.
I remember having nightmares with the other Twitter client that starts with a B. I had to sign in to twitter on my laptop and made the permission changes there to fix that very same annoyance. Bottom line here is to stay away from these client apps . Blaq it was..
Posted via CB10
Thanks guys. I think I might have tried an OS leaked update, then a restore when I was having problems with my screen. I guess that's where the problem started.
If I wait for the next official OS update (10.3.x should be coming soon to my Q10), will it fix this?
Thanks again!
Cvcv
This is a very common bug, not only for twittly but for most bb10 apps using hub integration. Mostly caused by using a leaked OS. nfortunately no fix from the developer can be done. It's Blackberrys job to fix because it's an OS issue
Here are similar issues:
http://forums.crackberry.com/showthread.php?t=994546
http://forums.crackberry.com/showthread.php?t=826196
http://forums.crackberry.com/showthread.php?t=993557
http://forums.crackberry.com/showthread.php?t=985973
I'm sorry but I can't help with this. Just a suggestion, delete app and restart phone. If it doesn't work I'm sorry.
Posted via CB10
I'm having this problem and I wasn't using a leaked OS.
Posted via CB10
Me too. Passport running PassportSQW100-1/10.3.1.2576 and I deleted twittly, this kept appearing in the hub, and I then reinstalled it and yet (even though it works fine) this password message still appears.
I'm wondering actually if it could be the cause of my poor battery life
Download ACCOUNTS CLEANER from BlackBerry world.
You should be able to fix your problem
My problem went away after my (official) update from 10.2.x to 10.3.x