You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 23, 2025. It is now read-only.
Copy file name to clipboardexpand all lines: .github/workflows/build_apk.yml
+88-11
Original file line number
Diff line number
Diff line change
@@ -391,16 +391,49 @@ jobs:
391
391
prerelease: true
392
392
body: |
393
393
This release was automatically generated from GitHub ${{ github.ref }} in run ID ${{ github.run_id }}.
394
-
arm64 is compatible with most devices and offers the best performance.
395
-
It is recommended to use "-signed.apk" releases to get the latest versions.
394
+
395
+
Summary:
396
+
- To install / update Kiwi Browser, use "Kiwi-${{ github.run_id }}-arm64-signed.apk".
397
+
If it doesn't work, try again using "Kiwi-${{ github.run_id }}-arm64-playstore.apk" (if it exists).
398
+
399
+
Detailed information about the different files:
400
+
- ".mapping" files are files that developers can use to investigate crashes, these files are not needed to run the browser and are for developers only.
401
+
- ".apk" files are packages that you have to install to use Kiwi Browser.
402
+
403
+
The filenames are in the form "Kiwi-[BUILD_VERSION]-[ARCHITECTURE]-[SIGNATURE_TYPE].apk"
404
+
405
+
Build version:
406
+
- Everytime a change is introduced in Kiwi Browser, a new build version is generated.
407
+
408
+
Architecture:
409
+
- "-arm64" is compatible with modern devices and offers the best performance.
410
+
- "-arm" is compatible with almost all devices and uses less memory.
411
+
- "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.
412
+
413
+
Signature type:
414
+
- On Android, applications have to be signed by a developer before they can be installed.
396
415
397
-
"-unsigned.apk" builds are signed using a random development key (upgrades / updates are not possible).
416
+
Kiwi has two types of builds:
398
417
399
-
"-signed.apk" builds are signed with the developer key (same as XDA-Developers, Discord and GitHub) and can be updated without data loss.
400
-
All builds are signed.
418
+
Signed by the developer:
419
+
- "-signed.apk" are builds signed using the official developer key.
420
+
A signed build is a build that comes straight from the GitHub official repository and is always the most updated.
421
+
422
+
Play Certified by Google:
423
+
- Once in a while, we send a "-signed.apk" build to be reviewed and signed by Google.
424
+
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".
425
+
426
+
We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.
427
+
428
+
This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".
401
429
402
-
"-playstore.apk" builds are signed by Google, they can be installed on top of Play Store releases only.
403
-
Not all builds are signed by Google.
430
+
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:
431
+
- 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.
432
+
- You cannot install a "-playstore.apk" build on top of a "-signed.apk" build.
433
+
434
+
Essentially, if you have a Google Play certified installation, you need to keep using the "-playstore.apk" files or the official updates.
435
+
436
+
There is generally only a few days only before the build appears on the Play Store anyway.
0 commit comments