Skip to content
Dashbud

Update Kuper

New Kuper versions bring fixes and new features. Updating usually takes a couple of minutes, but some versions also need small changes in your project. This page tells you which ones.

Step 1: Find your version and the latest one

Section titled “Step 1: Find your version and the latest one”
  • Your version is in buildSrc/src/main/java/Versions.kt:

    const val kuper = "x.x.x"
  • The latest version is: Latest version (ignore the v).

Step 2: Apply the changes for each version, in order

Section titled “Step 2: Apply the changes for each version, in order”

Look at the list below. Starting from the version right after yours, apply each version’s changes, one version at a time, until you reach the latest.

For example, if you’re on 2.3.0 and the latest is 2.3.7, apply 2.3.1, then 2.3.2, and so on. If a version isn’t listed, it doesn’t need any changes, so skip it.

Most entries link to a commit, a page on GitHub that shows what changed in each file. It looks like this:

A commit on GitHub, with the changed files on the left, and removed lines in red and added lines in green on the right
  • Red lines were removed. Delete them from your file.
  • Green lines were added. Add them to your file.
  • When only part of a line changed, that part is highlighted in a darker color.

Make the same changes in your project. You can skip changes to files you’ve customized with your own content, like icons, wallpapers or texts, unless the entry says otherwise.

Set kuper in Versions.kt to the latest version, then click File → Sync Project with Gradle Files and run your app to check that everything works. 🚀

Stuck on a version? Ask in the Discord server, and mention which version you’re updating from.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Also update the Gradle settings in Android Studio, as shown here:

Android Studio settings, in Build, Execution, Deployment, Build Tools, Gradle

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this comparison.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit and this commit.

Apply the changes in this commit and this commit.

You can now change the colors of snackbars. Set them up in your colors.xml file

Optional: if you want more customization options, apply the changes in this commit.

Apply the changes in this commit.

The frames_setup.xml file was split in 2 and the new dashboard_setup.xml has been created. Be sure to set them up.

The dashboard was rewritten from scratch, so it’s easier to start a new project from the sample. Save your assets and XML files first: most of them still work.

Show older versions

Add this line to the app’s AndroidManifest.xml

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Then delete the folder .idea/libraries/ and all build folders, and then restart Android Studio using the Invalidate Caches and Restart option.

Apply the changes in this commit.

Update the app/build.gradle and dependencies.gradle files.

Update the app/build.gradle and dependencies.gradle files.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit.

Apply the changes in this commit. Basically just some minor version updates.

  1. Update your build.gradle to match the new app/build.gradle file
  2. Update the proguard files:
  3. Changelog support has been added. Check how to set it up here.
  1. OneSignal plugin version is now explicitly defined due to some issues. Check the new app/build.gradle file here.

  2. Notifications are enabled by default now, if you don’t want them to be enabled you can easily set this config to false in app/src/main/res/values/frames_configs.xml:

<!-- Do you want notifications to be enabled for all your users?
- True means yes
- False means no
-->
<bool name="notifications_enabled_by_default">true</bool>
  1. Many things in the project changed, but it’s all for good. Please kindly check my last commit and apply these changes to your project :)

  2. Firebase is not used for notifications anymore. Start using OneSignal which is easier to setup. Tutorial available in wiki.

Basically just do what I did in this commit. 😅

Update these files:

  • app/build.gradle
  • app/proguard-rules.pro

Their content changed to fix some issues.

Some things changed in AndroidManifest.xml. Apply those changes in your projects too. Check what changed here

Made by Jahir Fiquitiva. Questions? Ask in the Discord server.