Releases: kiwibrowser/src.next
Generation 5848625449
Version 116.0.5845.70
including the following changes since: 2023-08-13T15:26:52Z
Date: Sun Aug 13 16:09:17 2023 +0000
Display a button to open a new tab, when Desktop mode is activated, and all tabs are closed
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 5848625449.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5848625449-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5848625449-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 5848538836
Version 116.0.5845.70
including the following changes since: 2023-08-13T15:26:52Z
Date: Sun Aug 13 16:09:17 2023 +0000
Display a button to open a new tab, when Desktop mode is activated, and all tabs are closed
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 5848538836.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5848538836-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5848538836-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 5848153874
Version 116.0.5845.70
including the following changes since: 2023-08-13T09:42:37Z
Date: Sun Aug 13 14:04:37 2023 +0000
Bump VERSION
Date: Sun Aug 13 13:50:59 2023 +0000
Resolve the case where newly opened tabs were not properly saved in the session when new tabs were opened in the background and the browser was immediately closed
Date: Sun Aug 13 12:58:36 2023 +0000
Change storage system that stores information about incognito tabs and tab groups
Date: Sun Aug 13 12:57:54 2023 +0000
Faster initialization of renderer on new tab
Date: Sun Aug 13 12:44:44 2023 +0000
Do not animate main menu items
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 5848153874.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5848153874-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5848153874-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 5846593622
Version 116.0.5845.69
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 5846593622.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5846593622-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5846593622-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 5846337368
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 5846337368.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5846337368-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5846337368-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 5843441868
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 5843441868.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5843441868-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5843441868-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 5842819861
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 5842819861.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5842819861-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5842819861-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 5842420565
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 5842420565.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5842420565-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5842420565-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 5835155316
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 5835155316.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5835155316-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5835155316-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 5810202119
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 5810202119.
Summary:
- To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-5810202119-github.apk".
If it doesn't work, try again using "com.kiwibrowser.browser-arm64-5810202119-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.