Saturday, December 22, 2012

Travel Expenses version 2.5.1

Version 2.5.1 of the Travel Expenses app will soon be available on Google Play.

This version is made up of one bug fix.

Bug fix:
  • For devices such as the nexus 7, android version 4.2, the user had to reset the device in order to retrieve exported files that were stored on external storage.
Current workaround:
  • Whilst connected over usb, toggle the connection type.
  • Reset the device.

Sunday, October 21, 2012

Travel Expenses version 2.5

Version 2.5 of the Travel Expenses app is now available on Google Play.

This version is made up of two enhancements and two bug fixes.

Bug fix:
  • If the app was not updated chronologically, the updates to the database would not be applied properly. For instance, if the user upgraded the app from version 1.5 directly to 2.4, then the app would crash on startup because of an inconsistent database. This issue has now been fixed.
  • If the android system returned a currency code which was invalid, the app would crash. This issue has been fixed.
Enhancements:
  • When the user is entering information in the "trip concerning" text box on the trip details screen, a list of corresponding recent entries is displayed, and the user may select one
  • When the user is entering a comment of an expense item, a list of recent corresponding comments is displayed, and the user may select one

Friday, August 3, 2012

Travel Expenses version 2.4

There was a bug in version 2.3 of Travel Expenses. Version 2.4 is a bug correction release.
If the user tried to export to csv or odt any expenses from a previous version where the currency had not been selected, the app would crash.


Tuesday, July 31, 2012



Travel Expenses version 2.3



Version 2.3 of the Travel Expenses app is now available on Google Play.

This version of the app will include the following new features:

  • For an expense item, the user will be able to select the currency used for the payment. By default the currency is the last currency selected, hence when adding several items in the same currency, the user will not have to reselect the currency for each item
  • The user will also be able to select which tender type was used for a payment. It can be either credit card, debit card, check or cash.

Thursday, July 26, 2012


Travel Expenses version 2.3



Version 2.3 of the Travel Expenses app is now in the testing phase.

This version of the app will include the following new features:

  • For an expense item, the user will be able to select the currency used for the payment. By default the currency is the last currency selected, hence when adding several items in the same currency, the user will not have to reselect the currency for each item
  • The user will also be able to select which tender type was used for a payment. It can be either credit card, debit card, check or cash.

Saturday, May 19, 2012

A bug in Android

There is a bug in Android version 2.3. Any device that runs this version(2.3, 2.3.1, 2.3.2 or 2.3.3) has a problem creating valid zip files. The zip files created can be opened in some decompressers, however others will complain that the format is invalid, and not unzip the file.

This is a problem for the Travel Expenses app, because it uses zip files for creating backups and restoring them. In addition, since the Open Document files are in fact zip files with another extension (the files are named .odt instead of .zip), these too are affected. When trying to open an Open Document file that's been created with the Travel Expenses app running on a Android 2.3.x device, the file may be unreadable to Open Office, Libre Office or MS Word.

I'm working on a solution to this problem.

The workaround that the user may try is the following (this is valid for both odt files and the backups of the database)
  • Create the Open Document export, or backup the database
  • Copy the file from the device to a computer
  • Rename the file with a .zip extension
  • Decompress the file with a decompressor that works (WinRar works)
  • Create a new zip file and add the files to it
  • Rename the file with the correct extension
  • Try to open the odt file in Open Office / Libre Office / MS Word
This problem has only recently come to my attention, hence no fix for this problem has been available earlier. 

Sunday, April 8, 2012



Travel Expenses version 2.1



Version 2.1 of the Travel Expenses app is now out on Google Play.

The version 2.0 of Travel Expenses contained an error due to the parameters used when compiling the app. Please accept my apologies for letting the error get though the testing stage.

The version 2.1 has had this issue fixed.

Saturday, April 7, 2012




Travel Expenses version 2.0



Version 2.0 of the Travel Expenses app is now out on Google Play.

This release includes the implementation of a new feature requested by a user.

The user may now select any third party app to use for the capture of images of bills and invoices. In order to set up the third party app, go to the setup screen, scroll down and click the select button on the "Image Capture" panel. To reset this configuration, and start using the default android camera, simply click the "Use default camera" button.

When on the expense details screen, with the Travel Expenses app configured to use a third party app, clicking the "Take receipt photo" will launch the third party app selected by the user.




Thursday, March 22, 2012




Travel Expenses feature request.




A user of the Travel Expenses app recently made a feature request on this blog. This is what the user posted as a comment to version 1.9:

Travel Expenses 2.0 is currently in the analysis phase for how this feature can be implemented. Briefly explained this is how the feature will appear in the app:
The user will be able to select which "Android Activity" should handle the digital copy of the invoice or bill the user is registering.

This feature will most likely be available in April 2012.

Wednesday, February 22, 2012





The Travel Expenses application version 1.9 has been published on the Android Market.



This is a bug fix release.
If the user entered an invalid number in the amount dialog, by pressing the "Amount" button on the expense details screen, or if the user didn't enter a number and clicked "OK", the text on the amount button would not be a valid number. This made the app crash when saving the information to the database, because it was unable to determine the amount (parse error).