Mobeasy — Release Builds

📱

APK

Direct install & testing

Install directly on any Android device (enable “Install from unknown sources”). Best for QA, demos, and sharing with testers.

≈ 109 MBarmeabi-v7a · arm64 · x86_64

⬇ Download APK

SHA-256
7935f61ee15d96450b5813c9f88cd6c4304c0460262168ee22e8101c2bd43e2e

🚀

AAB

Google Play upload

Android App Bundle — the format Google Play requires for new releases. Upload this in Play Console; Google generates per-device APKs.

≈ 77 MBPlay App Signing ready

⬇ Download AAB

SHA-256
c898c9084f53a469d23360c64e056214fd4b40ed7754579c1339d7fc7b424ef4

Build details

Application ID	com.mobeasy
Version name / code	4.2.3 / 102
compileSdk / targetSdk	36 / 36
minSdk	23 (Android 6.0)
Toolchain	AGP 8.11 · Gradle 8.14 · Kotlin 2.2 · Java 17
Flutter / Dart	3.41.7 / 3.11.5
Signing	release keystore (key.jks)
Source branch	chore/modernize-toolchain-and-bugfixes
Commit	405a799
Build type	release (minify off)

Install the APK (testers)

Download Mobeasy-4.2.3-b102-release.apk to the Android device.
Open it; if prompted, allow “Install unknown apps” for your browser / file manager.
Tap Install, then open Mobeasy and allow the notification permission.
Optional — verify integrity: sha256sum Mobeasy-4.2.3-b102-release.apk and compare to the hash above.

Upload the AAB (Play Console)

Play Console → your app → Testing → Internal testing (or Production) → Create new release.
Upload Mobeasy-4.2.3-b102-release.aab.
If Play rejects it as a duplicate, bump versionCode above 102 in android/app/build.gradle and rebuild.

⚠ Two things developers must know before a public release

Signing key is committed in the git repo (keyStore/key.jks + password in android/key.properties). For an internal/test track this is fine, but rotate the key and purge it from git history before shipping to production.
versionCode is still 102 (same as the previous store build). Increment it for any Play upload that must supersede an existing version.

ملاحظة للمبرمجين: مفتاح التوقيع مرفوع بالريبو — كافي للتجربة الداخلية، بس لازم يتدوّر ويتنظّف من تاريخ git قبل النشر الرسمي. وكمان رقم الإصدار (versionCode) لسا 102، لازم يترفّع لأي رفعة جديدة على Play.