⬆️ GH Action: EAS login issue, made neccessary changes.

.github/workflows/gh-actions-expo-build-staging.yml

@@ -31,25 +31,27 @@ jobs:
       - name: Setup Android SDK
         uses: android-actions/setup-android@v3
 
-      # Step 5: Install Expo CLI and EAS CLI, passing Expo token for authentication
+      # Step 5: Install Expo CLI and EAS CLI
       - name: Install Expo CLI and EAS CLI
-        uses: expo/expo-github-action@v8
-        with:
-          expo-version: "6.3.2" # Specify Expo CLI version for stability
-          eas-version: "3.7.2" # Specify EAS CLI version for stability
-          token: ${{ secrets.EXPO_TOKEN }} # Use Expo token for authentication
+        run: npm install -g expo-cli eas-cli
+
+      # Step 6: Authenticate with EAS using the token
+      - name: Authenticate with EAS
+        env:
+          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
+        run: echo "$EXPO_TOKEN" | eas login --token -
 
-      # Step 6: Install project dependencies with Yarn
+      # Step 7: Install project dependencies with Yarn
       - name: Install dependencies
         run: yarn install --frozen-lockfile
 
-      # Step 7: Build the Android APK using EAS
+      # Step 8: Build the Android APK using EAS
       - name: Build Android app
         run: |
           eas build --platform android --profile preview --local --output ${{ github.workspace }}/app-release.apk
         continue-on-error: false # Ensures the job fails on build error
 
-      # Step 8: Upload the generated APK file as an artifact for download
+      # Step 9: Upload the generated APK file as an artifact for download
       - name: Upload APK artifact
         if: success() # Run only if the build step succeeded
         uses: actions/upload-artifact@v4 # Updated to v4 to avoid deprecation