End of life

Even if your current AAPS system works exactly the way you like, upgrading is still worth it because newer releases bring safety fixes and bug corrections you may never notice until they matter, keep compatibility with new phone OS versions, CGM apps, pump firmware and Nightscout changes, add algorithm improvements and features that have been tested by the wider community, and ensure you stay on a version that is still supported and that others can actually help you troubleshoot. Some previous AAPS versions deliberately have no expiration date so they can keep working on older Android versions, so the lack of an expiration warning is not a sign that your version is still up to date or supported.

Each AAPS version can have an end date. After this date, AAPS may limit the loop. AAPS warns you before a version expires. Plan to update before the end date, and follow the update guide.

How to use this page

  1. In AAPS, open the menu (☰) at the top left and choose About. You will see your AAPS version there.

  2. Find the same version in the first table below. Read the end date next to it. Dates are written as year-month-day. For example, 2026-10-30 means 30 October 2026.

  3. Check the Release Notes and the update guide before you update. The version you can use also depends on your phone’s Android version.

The table does not show an end date for every AAPS version. If your version is missing, its end date may not have been set yet. This does not mean it will be supported forever.

AAPS version end dates

Loading AAPS version data…

Android API levels

Android gives each system version an API level, which is a number used by apps. For example, API level 30 is Android 11. The table below uses API levels from AAPS version data. The AAPS version in each row is the value listed for the API level shown. This is not a full list of versions you can install.

To choose an AAPS version for your phone, use the Android version guidance in the Release Notes.