[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
Riverturn Support • View topic - Release 0.9.4
Page 1 of 1

Release 0.9.4

PostPosted: Fri Feb 12, 2010 4:17 pm
by korey_sed
Did you know?
  • Due to popular demand, Black Swan will have a free ad supported version. We will start testing ads with the next release (not this one). Please show your support by clicking the ads occasionally.

New Features:

  1. Enable importing of contact pictures
  2. Enable importing of contact name prefix and suffix.

Changes:

  1. Automatic update sync with Google contacts so I'm always up-to-date
      Contacts are now Synced and not imported. This means that we only import the changes since the last sync which should be much faster. Also, contact sync now happens as part of the refresh process.

Bug Fixes:

  1. SMS badge is not updated after deleting an unread message
  2. Getting updates and login issues conflict
      This fix will only be noticeable with the next build, but what happens now is that when the app is updating itself, it will not login and do a refresh since it will have to restart after the updates anyways. This will also help when you have just changed you password and you get a login failure messages which may coincide with an update and cause you to have to wait for the update anyways before correcting your login.

Known Issues:

  1. DB update failure on application update
      You may get an database update failure after the application has finished updating. We have not found this to cause any adverse effects, so you can use the application by just relaunching it.
  2. Declining calls while the app is running causes it to stop working
      This is actually a Safari bug that may require a firmware update to fix, but for now either do not decline the call or just restart the application when this happens.