fix(ci): make sure that signing key doesn't include any whitespace before decoding

Author: NorbertKlockiewicz

.github/workflows/android-release.yml

@@ -55,11 +55,15 @@ jobs:
         uses: android-actions/setup-android@v3
 
       - name: Decode keystore
-        env:
-          KEYSTORE_BASE64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
         run: |
-          echo "$KEYSTORE_BASE64" | base64 -d > android/app/release.keystore
-          echo "Keystore decoded successfully"
+          # Decode keystore from base64 (secret is accessed directly, never echoed)
+          echo '${{ secrets.ANDROID_KEYSTORE_BASE64 }}' | tr -d '\n\r\t ' | base64 --decode > android/app/release.keystore
+          if [ -f android/app/release.keystore ]; then
+            echo "✓ Keystore decoded successfully"
+          else
+            echo "✗ Failed to decode keystore"
+            exit 1
+          fi
 
       - name: Create local.properties
         run: |

ANDROID_RELEASE.md docs/ANDROID_RELEASE.mdANDROID_RELEASE.md renamed to docs/ANDROID_RELEASE.md

@@ -2,7 +2,37 @@
 
 This document outlines the process for building and preparing Android App Bundles (AAB) for Google Play Console distribution.
 
-## Prerequisites
+## Recommended: GitHub Actions (CI/CD)
+
+**The preferred method is to build via GitHub Actions**, which handles all setup automatically and produces a downloadable AAB artifact.
+
+### Steps:
+
+1. Ensure version numbers are updated (see [RELEASE.md](./RELEASE.md))
+2. Go to **GitHub** → **Actions** → **"Android Release"**
+3. Click **"Run workflow"**
+4. Wait for the build to complete (~10-15 minutes)
+5. Download the AAB from **Artifacts** section at the bottom of the workflow run page
+6. Upload to Google Play Console manually
+
+### Required GitHub Secrets
+
+The following secrets must be configured in your repository (Settings → Secrets and variables → Actions):
+
+- `ANDROID_KEYSTORE_BASE64` - Your release keystore file (base64 encoded)
+- `ANDROID_KEYSTORE_PASSWORD` - Keystore password
+- `ANDROID_KEY_ALIAS` - Key alias
+- `ANDROID_KEY_PASSWORD` - Key password
+- `EXPO_PUBLIC_DETOUR_API_KEY` - Detour SDK API key
+- `EXPO_PUBLIC_DETOUR_APP_ID` - Detour SDK App ID
+
+---
+
+## Alternative: Local Build
+
+If you need to build locally instead of using GitHub Actions, follow these instructions.
+
+### Prerequisites
 
 ### 1. Development Environment
 

docs/RELEASE.md

@@ -0,0 +1,70 @@
+# Release Guide
+
+This guide covers the process for releasing new versions of Private Mind to the App Store and Google Play Store.
+
+## Version Bumping
+
+Before creating a release, update the version number in the following locations:
+
+### 1. App Version (Required)
+
+**File:** [app.json](../app.json)
+
+Update the `version` field:
+
+```json
+{
+  "expo": {
+    "version": "1.1.4"
+  }
+}
+```
+
+### 2. Android Version Code (Required)
+
+**File:** [android/app/build.gradle](../android/app/build.gradle)
+
+Update both `versionCode` (increment by 1) and `versionName` (match app.json):
+
+```gradle
+defaultConfig {
+    versionCode 60        // Increment this
+    versionName "1.1.4"   // Match app.json version
+}
+```
+
+### 3. iOS Build Number (Required)
+
+The build number should be set in `info` and `general` sections in Xcode, ensure the version matches `app.json`.
+
+## Platform-Specific Release Instructions
+
+### Android Release
+
+Android builds are automated via GitHub Actions. See [ANDROID_RELEASE.md](../ANDROID_RELEASE.md) for detailed instructions.
+
+**Quick Steps:**
+
+1. Update version numbers (see above)
+2. Commit and push changes
+3. Go to GitHub Actions "Android Release"
+4. Run workflow manually
+5. Download the generated `.aab` file from workflow artifacts
+6. Upload to Google Play Console manually
+
+### iOS Release
+
+iOS builds are created locally using Xcode.
+
+**Steps:**
+
+1. Update version numbers (see above)
+2. Open `ios/PrivateMind.xcworkspace` in Xcode
+3. Select "Any iOS Device" as the build target
+4. Choose **Product** -> **Archive**
+5. Once archiving completes, the Organizer window will open
+6. Click **Distribute App**
+7. Select **App Store Connect** -> **Upload**
+8. Follow the prompts to upload to TestFlight/App Store
+
+For detailed iOS publishing instructions, refer to the [React Native Publishing to App Store guide](https://reactnative.dev/docs/publishing-to-app-store).