Generation 1004568917

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 1004568917.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 999038253

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 999038253.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 998800620

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 998800620.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 995463031

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 995463031.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 994167097

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 994167097.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 988737166

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 988737166.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 984907676

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 984907676.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 982475721

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 982475721.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 974744797

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 974744797.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.

Generation 974529481

This is a preview version of Kiwi Browser called Kiwi Browser Next, it will install as a separate application next to the regular Kiwi Browser.

It is work-in-progress so it is very buggy and some functionalities are still missing.
Do not store important information in Kiwi Browser Next as it is a test version that is created just for early testers of this new version of Kiwi Browser based on Chromium 93.

In a couple of days, after all the fixes are done, Kiwi Browser Next is going to disappear and become Kiwi Browser.

This release was automatically generated from GitHub refs/heads/master in run ID 974529481.

Summary:

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

Detailed information about the different files:

• ".mapping" 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 "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"

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:

• "-signed.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 "-signed.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 "-signed.apk" build on top of a "-signed.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 "-signed.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 "-signed.apk" version.