Archive for the 'Bugs' Category

Make the jump to 2.0

Published
by
Paul Stringer
on October 3, 2008
in Bugs, Development and iPhone
. 5 Comments

When releasing the new TMT for iPhone 2.0 app I made a couple of changes under the hood of our API. One of the things we did was to remove and clean up a couple of patches that were in there to accommodate a couple of bugs in the first TMT for iPhone app v1.0.

These bugs mostly arise around issues to do with & and = signs in messages. If you’re still using the old app you’ll have discovered messages containing these characters no longer save, anyone who gets a lot of messages with smilies in such as =) will notice this a lot.

To avoid confusion about what’s going on here we’ll be deprecating the API key for the v.1 app in the next few days. The app will try to reauthorise but you’ll be getting instead a nice message asking you to upgrade to 2.0.

So for original iPhone 2G with iPhone Software 1.* hold outs if there weren’t enough reasons already to get yourself to 2.0 this is just one more, don’t be scared now it’s real easy.

TMT for iPhone 2.0 Instructions

UPDATE Friday 17th October - Today we disabled the original iPhone 1.0 app.

RSS feeds not working today. Sorry! :(

Published
by
Katie
on March 26, 2008
in Bugs
. 0 Comments

The RSS feeds are not working today. We disabled them when we found they were generally slowing things down disproportionately. So the site’s working OK even with a rather nice increase in traffic following a few lovely blog posts, but RSS isn’t. Hope to have that back up and running very soon.

DNS Issue!

Published
by
Katie
on March 18, 2008
in Bugs
. 0 Comments

If you’re seeing the Treasuremytext blog (this page) when you wanted Treasuremytext.com its because we’re having a little problem with our DNS. It will be resolved soon. We hope. For now use the Beta site link to get there

Sorry about the emails and SMS

Published
by
Paul Stringer
on March 17, 2008
in Beta and Bugs
. 0 Comments

We had a bit of an error this morning whilst testing something that resulted in the site sending lots of email/sms messages to everyone subscribed to my TextStream. Sincere apologies if you were one of the recipients. Preventative measures are being taken to stop it happening again, but enough excuses because it shouldn’t have happened in the first place.