I thought Id take a moment and describe all the ways that I know of. In case anybody should need them. There are two ways to get your data back, either you can extract data from an iTunes backup or you can extract it directly from your iDevice.

Extract data from iTunes backups

There are several tools available for extracting data from iTunes backups.
Basically what these tools do is show you a list of all your iTunes backups. When you select one of them you get access to your iDevices file structure as it was when you made the backup. It is important to know that if you have selected to encrypt your backups, the information you extract is encrypted aswell. Even if it is possible to decrypt it, it is tedious and time consuming.
Lets say you want to retrieve your MyWallet+ database from an iTunes backup, these are the steps necessary:

Mac

1. Download the iPhone Backup Extractor from http://supercrazyawesome.com/
2. Install and start the iPhone Backup Extractor
3. Click “Read backups”
4. Select one of your backups, preferrably the latest one, and press “Choose”
5. Look for “com.block21.minautgifter”, select it and click “Extract”
6. Navigate to the desktop and click “Extract here”
7. Now you should have a folder called “com.block21.minautgifter” on your desktop. In this folder you should be able to find files that end with “.sqlite” or “.mw”. These are databases that contain your data.

PC

1. Download the iPhone backup extractor from http://www.iphonebackupextractor.com/
2. Install and start the software
3. In the dropdown below “Select backup”, select the latest one
4. Click “Expert mode”
5. You are presented with a directory structure snapshot of your iDevice from the moment when you created the backup
6. Look for “Applications”, open it and then look for “com.block21.minautgifter”, open it aswell
7. Look for the “Expenses.sqlite” file, usually placed inside the “Library” folder, and check it
8. Now, the “Extract selected” button will get enabled – click it.
9. Choose the target directory, for example the desktop, click Ok
10. Now you should have a folder called “application” on your desktop. Inside it you will find “com.block21.minautgifter” and in it “Library”. In this folder you should be able to find “Expenses.sqlite”. This is the database file that contains your data.

In order to restore one of these backups, read the steps described in the “Restore” paragraph below.

Extract data from your iDevice

There are tools for accessing the filesystem on your iDevice. iExplorer is easy to use and available for both platforms.

iExplorer (Mac and PC)

1. iExplorer is available for both Mac and PC, get it from: http://www.macroplant.com/iexplorer/
2. Connect your iDevice to your computer
3. Install and start the software
4. Make sure your device is selected in the top left corner
5. Open the “apps” folder and look for “com.block21.minautgifter”
6. Open it and look for the “Library” folder
7. If there is a file called “Expenses.sqlite”, it is your current database. In case you have had issues with your database, there might be a file called “Expenses~.sqlite” too.
8. Extract files by dragging them to your desktop

In order to restore a database file, read the steps described in the “Restore” paragraph below.

Restore

There are multiple ways to restore a backup file. Through Dropbox or through iExplorer.

Dropbox

1. First of all, you need to create an account at http://www.dropbox.com
2. Log in to your dropbox.com account and create a folder called “MyWallet”
3. If your database is called “Expenses.sqlite”, rename it to “Expenses.mw”
4. Upload it to your “MyWallet” folder in your dropbox account
5. Start MyWallet on your iDevice
6. Go to “Settings” and select “Backup”
7. Press “Connect to Dropbox”
8. Log in to your account
9. If you were logged in, you are presented with the option to “Restore backup from Dropbox”, press it
10. This should display a list of backups, press the one you uploaded
11. Thats it!

iExplorer

1. iExplorer is available for both Mac and PC, get it from: http://www.macroplant.com/iexplorer/
2. Connect your iDevice to your computer
3. Install and start the software
4. Make sure your device is selected in the top left corner
5. Open the “apps” folder and look for “com.block21.minautgifter”
6. Open it and look for the “Library” folder
7. If there is a file called “Expenses.sqlite”, it is your current database
8. If you want to restore another database, you must replace the existing “Expenses.sqlite”
9. Thats it, start your app and your good to go

Automatic backup feature
That is why were introducing an automatic backup feature in the next version. It will silently, and automatically, make backups of your database on a daily basis. We will probably limit it to 5-10 simultaneous backups, which means that the oldest backup is continuously pushed out. This is to ensure that you NEVER EVER again loose your data due to bugs or to any misfortune.

We have had our share of database issues in the last few versions.
The reason for these issues is that under the surface, there are huge changes in the apps database. This is due to the amount of feature requests we get, and frankly – if we dont grow and add features – we might aswell stop developing. We have expanded the database to support budgets, labels, reports and a dozen of other features we have planned for this year. Database migrations are always difficult, especially since we have so many users that are running so many different versions of the app on a wide variety of devices.

Financial analyzer
It is finally time to reveal the financial analyzer!
We’ve been working with this feature for some time and its ready to be released.
A lot of users have requested all kinds of visualizations of their data. Bar charts, pie charts, comparisons etc. We have been sceptical to showing graphs mainly because it is really hard to fit a good looking and USABLE graph into an app in portrait mode.
But we think we’ve figured out how to do it.

Screenshot:

Here is a short video clip of the pie chart component that we’ve developed for the Financial Analyzer.

Wanna help?
We need the following strings translated:

• “You dont have enough data to show the chart”
• “Average income per day”
• “Average expense per day”

..into: Norwegian, German, Spanish, French, Dutch, Russian, Portugese, Italian, Japanese, Korean, Chinese, Danish, Finnish, Hungarian.

Released 23 april 2012

Users who have used the app more than 1,5 year are the ones who are affected by this bug.
If you are affected by the bug, please know that your data is safe and this release will fix the problem.

Date submitted: 2012-03-01
In review: 2012-03-08

Do you want to help us?
These are the strings we need translated:

• “Account”
• “Accounts”
• “Account name”
• “Initial balance”
• “Edit account”
• “Create account”
• “Current balance”
• “Select account”
• “Select accounts”
• “Balance on %DATE%”
• “Transfers”
• “Transfer”
• “From account”
• “To account”
• “You must have atleast one account.”
• “Delete account”
• “All transactions will be deleted if you choose to delete the account.”
• “Add new account”

The languages we need these string in are:
German, Spanish, French, Dutch, Russian, Portugese, Italian, Japanese, Korean, Chinese, Danish, Norwegian, Finnish, Hungarian

E-mail the translated strings to support@block21.com

The accounts feature has been finished for about a month now.

But, we have had our share of issues with the latest versions so we’ve invested alot of time in profiling and debugging the app in general. Although the majority of our users never even come across bugs, we want to make sure the app is as rock solid and stable as possible.

Anyhow. Full time work means that from now on, you can expect even more frequent updates from us!

Thank you for your patience and for your support.

1. An Australian fellow (AppStore signature “PASRev”) commented on an translation bug when you delete categories. After further investigation, I can confirm that the bug “only” affects English, French and Portugese. The string in question is: “The category you are about to delete has X subcategories and Y transactions. These will also be deleted if you tap OK”.
2. Added account management (adding, removing, editing, sorting – in Settings)
3. Added account selection (in “New transaction”)
4. Added transfer between accounts (in “New transaction”)
5. Added possibility to set a default account (if you have multiple). If you only have one account, all transactions will be registered into that account by default.
   Accounts are not mandatory, you will be able to use the app without the accounts feature.
6. BUGFIX Fixed a bug with the recurring transactions.
   The bug occurs when the recurring transactions are created/updated and is caused by the spinning progress view switching between calculating and creating transactions.
   To be safe, we advice you not to create new recurring transactions until this version has been released.
7. BUGFIX Fixed a bug with the recurring transactions. Some users reported of problems with duplicate transactions being generated.
8. Major stability improvements

Screenshots:

Planned submit date: 2012-01-03
Postponed submit date: 2012-02-19
Actual submit date: 2012-02-20
Release date: 2012-02-29

I’ve implemented iCloud support for MyWallet+. But I think its too easy to create situations where data that is shared between several units will get corrupted. The most hazardous situations I’ve come across are the following:

1. Core Data: Related data
   Referential integrity must be handled manually. This is sort of a drag. A tedious drag if you consider that all relationships in your database must have their own, specific, referential integrity code that validates and redeems synchronization requests between units.
2. Migration from non-iCloud to iCloud DB
   I’ve not yet found an quick and safe way to migrate an existing Core Data database to iCloud. The only really safe way to do this is by performing an export to an intermediary format and then importing it, record by record. If you’ve got a decent sized database, it will be time consuming. Uncool.

This does not mean that we wont add iCloud support to My Wallet+.
It only means we’re going to make really sure that it works flawlessly before releasing it.
Simple as that. Anything else would be irresponsible.

Update 20 December 2011
There actually is a preferred way of accomplishing issue #2 (above). I’ve just completed the implementation of the migration function. This means that all your existing MyWallet+ databases will be automatically moved into iCloud, and it wont take forever (2-10 seconds).

This version is a hotfix, but it contains alot of changes. Most of them are not visual – but nevertheless very important. It will upgrade your databases to one that supports accounts, budgets (and more neat, secret, stuff! ).

Change log

1. Completely rewritten Core Data stack
2. Added safe database migration wizard (no more timeouts on older devices!)
3. Moved database from Documents folder to Library folder
4. iCloud preparations (Completed implementation, but it needs further testing.)
5. Accounts preparations (Database extended to support accounts)
6. Budgets preparations (Database extended to support budgets)
7. Import preparations (Support for iTunes document management)
8. Landscape financial analyzer v1 (Line chart, Pie chart, Bar chart and more!) Didnt make it in this version.
9. Search: Totals (Shows separate sums of incomes/expenses)
10. Intelligent sort in autocomplete (frequent expenses appear on top)
11. Preparations for decorating categories with icons

Planned submit date: 2011-12-15
Actual submit date: 2011-12-18
Release date: 2011-12-21

We are currently analyzing the logs and testing on our 3GS units to find it.

Many reviewers are complaining about this problem, that mainly affects iPhone 3GS with iOS 5.0.1. We are terribly sorry for the inconvenience and we will post a new version as soon as possible.

Thank you for your patience and support.

Update 21 November 201, 0:55 am
We have isolated the problem and we’re working on a solution.
A fix should be available within a couple of days.

Planned submit date: 20 November 2011
Actual submit date: 21 November 2011
Release date: 1 December 2011

This is whats been done on 1.090:

• LLVM 3.0 bug
  In XCode 4.2 the compiler (LLVM 3.0) has a bug that causes the app to crash on iPhone 3G/3GS and iPod 2nd gen.
• XML Export
  The XML format is our custom format. This will mainly be used for backups and migrating to/from Android
• Password
  We’ve rewritten the password dialogue from scratch. Its a bit prettier and has no animations
• Language bugfix
  Minor language bugfix in the settings. Sections were always set in Swedish.

The landscape graph is completed, but we need to do some testing on older units before its ready for production.
We will post some new screenshots during this week. Stay tuned!

Planned submit date: 1st November 2011
Actual submit date: 4th November 2011
Release date: 10th November 2011