Introduction

When using Expo’s EAS Build, the output is an .aab (Android App Bundle) instead of an .apk. However, .apk files are often needed for local testing and sharing. In this guide, we’ll walk through how to convert .aab to .apk using simple commands on Windows and macOS.

Prerequisites

• Java Development Kit (JDK) installed (for bundletool.jar).

• The .aab file generated from Expo EAS Build.

• Android SDK (adb) installed for testing.

Step 1: Download bundletool.jar

Download Google's official BundleTool:
👉 Download bundletool.jar

Save it to an accessible location, e.g., Downloads.

Step 2: Generate the APK from .AAB

Run the following command:

java -jar bundletool.jar build-apks --bundle=myapp.aab --output=myapp.apks --mode=universal

This creates a .apks archive containing the .apk file.

Step 3: Extract the APK

Rename the .apks file to .zip and extract it. You’ll find your .apk inside the universal folder.

Alternatively, extract it via command line:

unzip myapp.apks -d myapp_apks

Find the APK at:

myapp_apks/universal.apk

Step 4: Install the APK on Your Device

To install the APK, connect your Android device via USB and run:

adb install myapp_apks/universal.apk

Conclusion

You’ve successfully converted an .aab to an .apk for testing! 🎉

Introduction

So, you've built a fantastic React Native app with Expo, and now you're eager to publish it on the Google Play Store. But wait—how do you generate a production-ready APK? Worry not! In this guide, I'll walk you through the entire process step by step.

Step 1: Install Expo CLI (If Not Installed)

First, ensure you have Expo CLI installed. If not, run:

npm install -g expo-cli

Also, make sure you’re logged in to your Expo account:

expo login

Step 2: Configure Your App

Before generating the APK, check your app.json or app.config.js file. Update the necessary details like the app name, package name, and version.

Example app.json:

{
  "expo": {
    "name": "MyAwesomeApp",
    "slug": "myawesomeapp",
    "version": "1.0.0",
    "orientation": "portrait",
    "icon": "./assets/icon.png",
    "android": {
      "package": "com.yourcompany.myawesomeapp",
      "versionCode": 1,
      "permissions": []
    }
  }
}

Ensure that android.package is unique (matching your domain, like com.yourcompany.myapp).

Step 3: Build the APK File

Since Expo no longer supports “expo build:android”, you’ll need to use EAS Build instead. Run the following command:

npx expo install eas-cli

Then, initialize EAS:

eas build:configure

Now, to build an APK, use:

eas build -p android --profile preview

This will generate an APK for testing purposes. For a Play Store-ready build, use:

eas build -p android --profile production

Once the build is complete, you’ll get a download link for your APK/AAB file.

Need to Convert .AAB to .APK?

If you want to generate an APK from an AAB file for testing, check out this guide.

Step 4: Sign Your APK (If Required)

Expo automatically handles signing, but if you want to manage keys manually, generate a keystore:

eas credentials

Follow the prompts to generate and download your keystore.

Step 5: Test Your APK on a Physical Device

Download the APK file and install it on your phone:

adb install myapp.apk

Alternatively, share the download link generated by Expo.

Step 6: Submit to Google Play Store

1. Create a Google Play Developer Account

If you haven’t already, register at Google Play Console (one-time fee of $25).

2. Create a New App

• Click Create app

• Set your app name, language, and category

• Choose App (not Game) and Free/Paid option

3. Upload Your AAB File

Since Google now requires AAB instead of APK, make sure you generated the AAB file (--profile production). Upload it under Production > Create new release.

4. Complete Store Listing

• App Name & Description

• Screenshots (Minimum 2, for phones and tablets)

• Feature Graphic (1024x500 px)

• Privacy Policy URL

5. Submit for Review

Once everything is set, click Submit for Review. Google will review your app (typically within 2–7 days).

Conclusion

Congratulations! 🎉 You've successfully created a production-ready APK (or AAB) and submitted your app to the Google Play Store. Now, grab some chai ☕ and wait for your app to go live!

If you found this guide helpful, share it with your fellow developers. 🚀 Happy coding!

🛡️ Why You Need SSL (And Why Google Hates You Without It)

Ever visited a website and saw "Not Secure" in the address bar? That’s basically Google screaming, "RUN! THIS WEBSITE IS A SCAM!"

SSL (Secure Sockets Layer) encrypts the data between your website and visitors, making sure hackers can't steal login details, credit card info, or even your embarrassing search history.

So today, we’re going full Tony Stark and putting a protective shield (SSL) on your website. Let’s get started! 🚀

🔧 Step 1: Install Certbot (Your SSL Fairy Godmother)

Certbot is the magic tool that handles SSL setup. Run this command like a boss:

sudo apt-get install certbot python3-certbot-nginx

🛑 Possible Error: "Command not found"

This means your Linux system is missing the required repositories.
Run this first:

sudo apt update && sudo apt install software-properties-common

Then, try installing Certbot again.

✅ Once installed, let’s move to the next step.

🌍 Step 2: Get Your SSL Certificate (Make Google Happy)

Time to convince Google that we are a trustworthy citizen.

🔹 To secure your website (abhishekanandok.com and www.abhishekanandok.com), run:

sudo certbot --nginx -d abhishekanandok.com -d www.abhishekanandok.com

What Happens Next?

Certbot will now act like a strict visa officer and ask you:

1. Your Email (For SSL renewal notifications)

   • Enter your best email unless you enjoy surprises when your SSL expires.

2. Agree to Terms? (Y for Yes, unless you want to live dangerously)

3. Would you like to share your email? (N because we all get enough spam already)

🤖 Step 3: Secure Your API Too (Because It’s Lonely)

If you have an API (api.abhishekanandok.com), it also needs SSL to avoid angry red warnings from browsers.
Run this:

sudo certbot --nginx -d api.abhishekanandok.com -d www.api.abhishekanandok.com

🔄 Step 4: Make SSL Renew Automatically (So You Can Relax)

Let’s Encrypt SSL expires every 90 days (because they like to keep us on our toes). Instead of manually renewing it like an unpaid intern, automate it with:

sudo certbot renew --dry-run

If you see "Congratulations! Dry run successful!", your SSL will renew itself like magic. ✨

🛑 Possible Error: "Too many requests"

Let’s Encrypt has rate limits (because of people who abuse the system).
Wait for a few hours and try again.

🎉 Congratulations! You’re Now SSL Certified!

Your website is now rocking a padlock icon and looking super professional. No more "Not Secure" warnings, and Google will finally stop judging you.

✅ What’s Next?

• Test your SSL here: SSL Checker

• Enjoy the trust and love of your visitors

• Share this guide with friends who still live in the "HTTP dark ages"

Happy Securing! 🔒✨🚀