Threaded Mode | Linear Mode

elliott94 · 06-13-2009, 05:46 PM

Hi,
A few days ago I installed Tweets60 onto my Nokia N95 8 GB. The program was working fine until today.
I launched TweetS60 from my standby screen. When the access point sollection dialog appeared, instead of pressing select on my access point (O2 mobile web), I hit the cansel option. I exited the program and relaunched it. When I hit select on my access point, the program was able to fetch some of my tweets, but half way through it exited.
Once again I launched it, and it did the same thing.
The third time, instead of selecting my access point straight away, I hit cansel on the first prompt and selected it the second time it asked me. It was able to fetch tweets, but after 5 minutes when it tried again it exited.
Do you know what the problem could be?
I've tried rebooting my phone and reinstalling the application, but it hasn't sulved the issue.
Thanks in advance,
Elliott.

boydknife · 06-14-2009, 11:13 PM

this is most likely caused by the noted bug in twitter about 32 bit integers or something of that sort. a bunch of twitter apps have crashed including twitteriffic. as of now, i'm using twittix, since it is not broken. hopefully someone will update twitter s60, but since it's free... i won't hold my breath.

(06-13-2009 05:46 PM)elliott94 Wrote: Hi,
A few days ago I installed Tweets60 onto my Nokia N95 8 GB. The program was working fine until today.
I launched TweetS60 from my standby screen. When the access point sollection dialog appeared, instead of pressing select on my access point (O2 mobile web), I hit the cansel option. I exited the program and relaunched it. When I hit select on my access point, the program was able to fetch some of my tweets, but half way through it exited.
Once again I launched it, and it did the same thing.
The third time, instead of selecting my access point straight away, I hit cansel on the first prompt and selected it the second time it asked me. It was able to fetch tweets, but after 5 minutes when it tried again it exited.
Do you know what the problem could be?
I've tried rebooting my phone and reinstalling the application, but it hasn't sulved the issue.
Thanks in advance,
Elliott.

jenson · 06-15-2009, 04:41 AM

(06-14-2009 11:13 PM)boydknife Wrote: this is most likely caused by the noted bug in twitter about 32 bit integers or something of that sort. a bunch of twitter apps have crashed including twitteriffic. as of now, i'm using twittix, since it is not broken. hopefully someone will update twitter s60, but since it's free... i won't hold my breath.

(06-13-2009 05:46 PM)elliott94 Wrote: Hi,
A few days ago I installed Tweets60 onto my Nokia N95 8 GB. The program was working fine until today.
I launched TweetS60 from my standby screen. When the access point sollection dialog appeared, instead of pressing select on my access point (O2 mobile web), I hit the cansel option. I exited the program and relaunched it. When I hit select on my access point, the program was able to fetch some of my tweets, but half way through it exited.
Once again I launched it, and it did the same thing.
The third time, instead of selecting my access point straight away, I hit cansel on the first prompt and selected it the second time it asked me. It was able to fetch tweets, but after 5 minutes when it tried again it exited.
Do you know what the problem could be?
I've tried rebooting my phone and reinstalling the application, but it hasn't sulved the issue.
Thanks in advance,
Elliott.

I've encountered the same issue too. Seems like we need to wait for updates or pay for another Twitter client

**Chris** · 06-16-2009, 08:30 AM

Version 1.26 is out now and should fix this problem.

Sorry it took so long, we only spotted the problem on Friday evening and nobody was available until yesterday to fix it!

boydknife · 06-16-2009, 01:25 PM

awesome, thanks!

(06-16-2009 08:30 AM)Chris Wrote: Version 1.26 is out now and should fix this problem.

Sorry it took so long, we only spotted the problem on Friday evening and nobody was available until yesterday to fix it!

jenson · 06-18-2009, 02:52 AM

(06-16-2009 08:30 AM)Chris Wrote: Version 1.26 is out now and should fix this problem.

Sorry it took so long, we only spotted the problem on Friday evening and nobody was available until yesterday to fix it!

Awesome + Greatwork! Late is better than no action!

Thanks!

Regards,
Jenson