Generation 5601022637

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5601022637.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5601022637-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5601022637-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5600729543

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5600729543.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5600729543-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5600729543-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5600518697

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5600518697.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5600518697-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5600518697-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5588535544

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5588535544.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5588535544-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5588535544-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5587800410

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5587800410.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5587800410-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5587800410-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5579794346

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5579794346.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5579794346-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5579794346-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 5579034394

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 5579034394.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5579034394-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5579034394-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 4736345870

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 4736345870.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-4736345870-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-4736345870-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 4736000092

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 4736000092.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-4736000092-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-4736000092-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Generation 4735067711

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 4735067711.

Summary:

• To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-4735067711-github.apk".
  If it doesn't work, try again using "com.kiwibrowser.browser-arm64-4735067711-playstore.apk" (if it exists).

Detailed information about the different files:

• ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
• ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

• Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

• "-arm64" is compatible with modern devices and offers the best performance.
• "-arm" is compatible with almost all devices and uses less memory.
• "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

• On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

• "-github.apk" are builds signed using the official developer key.
  A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

• Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
  Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

• You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
• You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.