This page last updated
07.05.2025
Version released 07 May 2025.
For technical reasons, the Android variant of this version is not available on Google Play. It can be downloaded from the Kippsware web site.
For shopping list functions, versions 1.2.0 and above are compatible with IK-Shop from V 1.6.0 upwards. Version 1.2.0 or a later version of this app and version 1.6.0 (or a later version, as available) of IK-Shop must be installed if shopping list functions are to be used.
We are not aware of any current problems.
This is basically a technical update for maintenance reasons. Some minor errors have been corrected.
The "Reset database" function is available in all variants, see Kippsware Common Functions / Reinitialising the database.
In desktop variants, the recipe detail window has been reconfigured to allow multiple recipes to be visible at the same time.
The changes affect only the Android version
The Android variant has been update for compatibility with Android V 14.
Problems with native synchronisation (server error reported) have been resolved.
This version is compatible with the current version of the licence server. There are no changes to the documented licensing procedure. However, licenses that have already been installed will be reset and the software must be relicensed. The licenses available to a user will not be reduced by this procedure.
The software now supports the synchronization method "native synchronization" as well as synchronization via Dropbox.
An issue with synchronisation on Android devices has been corrected. This problem could cause changes made on an Android device to be lost on synchronisation, and in some cases might have caused a program crash.
Initialisation on Android uses correct preset data, as specified in startup dialogue (this problem was not present in desktop variants).
Handling of the on / off switch for help texts now works correctly on all variants.
Both the Android and desktop variants of this version use the kippsware licensing model. It follows that the Android variant is not available on Google play, but can be downloaded from our download page .
The help functions reference the (new) web site kippsnet.eu.
Minor error corrections.
A problem with automatic synchronisation, which arose in V 1.5.8, has been resolved. Synchronisation now operates as documented.
Minor error corrections, including resolution of obscure problems in the calendar which could cause the app to freeze on certain days when using certain calendar functions.
Sorting and display of recipes now uses the collation sequence of the current locale. The main difference for latin characters is that accented characters are treated as directly following their unaccented equivalent.
Help switch off / switch on restores the state of show / don't show of individual texts to what it was before the swtch off. Reactivating all help is an option.
Changes to adapt to new interfaces implemented by Dropbox (in detail: Dropbox core SDK V 4.0.0, should you want to know) have been implemented.
This is transparent to the user - there is no new functionality - except that special action is required on the first synchronisation following
installation of the this update.
On the first synchronisation after update to this version, the Dropbox interface will reject the synchronisation with the message "Refresh token not
available". Repeat the synchronisation operation. You will be requested to re-authorise the app with Dropbox. After this has been done,
synchronisation will proceed as normal. Further synchronisations will function (as before) without further explicit authorisation. This procedure is
necessary on all devices.
Corrections have been made to the in-app licence purchase procedure.
Inserting a menu item in the calendar for December failed if the day selected was in the first days of the following January. This has been corrected.
Automatic synchronisation in all variants now behaves as specified in the option settings.
Processing of conflict situations on synchronisation has been updated. This should resolve a number of problems associated with deleting records in one device before synchronising, and should now avoid certain unjustified synchronisation error messages after updating the menu calendar.
This version corrects an error in the calendar concerning the display and update of the last days of December. Days at the end of December that appeared in the calendar display for January could not be updated as expected and attempts to edit these days could cause a program crash.
Some improvements have also been made in the handling of filters.
Displays of help texts should now be suppressed correctly when the "Do not show this again" box is checked.
In Version 1.5.0, filter settings that were active when the app was terminated could be duplicated on restart.
The additional filters appear in the edit/delete lists for filter processing (Long press the "Filter" button in the dish list display to access these functions) and can be deleted using the "Delete" function.
This issue only affects the Android variant. The Android Version 1.5.1 is fully compatible with the desktop version 1.5.0.
Database handling on save / restore has been reworked to provide better error recovery in the case that files cannot be found or cannot be read or written.
A problem that prevented the Android variant from registering itself as a dropbox client has been resolved. Connection to Dropbox and synchronisation now function as documented.
The program icon has been modified to distinguish it from other KippsWare applications.
An install package for Mac OS X is now available.
The Android variant now conforms to the latest Google guidelines (targets Android level 28).
If the focus in the calendar is on the day that is is the first day not shown on the previous month's calendar, the app would crash when the calendar was changed to show the previous month. Specifically, with the calendar setting "1st. day of week is Monday", 1st. June 2019 is a Monday and does not show in the calendar for May. If this day had the focus, changing the calendar to May would cause a crash.
This problem has now been corrected.
Automatic synchronisation is now performed correctly in the Android variant on app startup, if this option is set.
A problem with accessing context menu of calendar immediately after startup resolved.
Minor error corrections have been implemented. These should improve stability but have no functional significance.
The appearance of the Android variant has been improved, particularly in dialogues, and the software should adapt better to different screen sizes and resolutions.
The checkbox "Don't show this again" is now handled correctly for all for all panel hint displays. This change only affects the Android variant.
Changes have been made to ensure compatibility with newer versions of Android (specifically, API Level 26). The user may see new system dialogues requesting permission to access external storage. Such access is required for the database backup and restore features. This only affects the Android variant.
Due to an error in the generation procedure, the Verion 1.3.2 for Android could not synchronise correctly with the desktop (PC) variant. To recover: install V 1.3.3 on all Android devices. Then, on the device that has the most up-do-date data (PC or Android), perform a synchronisation with the option "Overwrite master". Then perform a normal synchronisation on other devices.
A problem arising from certain cut/swap/paste operations in the calendar could result in corruption of the database, preventing a restart of the app. This problem has been resolved. Databases from V 1.3.1 suffering from this error can be read and will be automatically corrected in this version.
Desktop variant only
On startup, the calendar now always displays the current month.
The download file for the desktop installation is considerably smaller that in previous versions, due to use of an optimiser. This is not an indication of an error and has no effect on the executing program.
An error in the generation of V 1.3.0 made it impossible to define new dishes. This issue has been resolved.
A number of problems in connection with date-dependent dishes (i.e. dishes that should only be eaten at certain seasons or on certain days) have been corrected. The specification of a minimum interval between two meals containing a certain dish is now handled correctly and is used as expected in the "date-dependent" filter.
Setup dialogues for the date-dependent information have been changed. The "Minimum interval" attribute is now set in the same dialogue as other date-dependent attributes (weekdays, seasons). Dishes with date-dependent attributes are indicated as such in the dish list (Android: by colour. PC: by textual note).
The online documentation has been updated.
Some minor problems with the "About" display have been identified and corrected.
Minor corrections to improve stability have been made in all variants.
A problem with navigation to next / previous months when a month spans six calendar weeks has been resolved.
Android variant only
The format or the calendar has been changed slightly. Additionally, it is possible to navigate to the next/previous month and the next/previous year by swipe left/right (for month) or swipe up/down (for year). The next/previous buttons are still available.
Dishes for which no recipe is defined, but which have a defined shopping list in IK-Shop, are indicated in the dish list with a green pencil symbol. The symbols for dishes with recipes which have shopping lists are unchanged.
Shopping lists are now supported for both recipes (as before) and for dishes without recipes (new). IK-Shop V 1.6.0 contains a new function for creating shopping lists requirements for dishes.
Some optimisations have been introduced into the synchronisation process. These should not affect the user interface.
Format changes and format corrections have been made to some displays. We have also corrected some cases where texts were displayed in the wrong language.
Attempts to synchronise the database with a database created by a newer version of the software than that on the device (this can arise if the software is not updated on all devices at the same time) will now be rejected. Previously, this situation could lead to a program crash.
A number of internal changes to improve stability have been made.