Enter build numbers manually for production OTA deploys (#11289)

Co-authored-by: Claude <noreply@anthropic.com>

scripts/useBuildNumberEnv.sh

@@ -3,9 +3,19 @@ set -o errexit
 set -o pipefail
 set -o nounset
 
-outputIos=$(eas build:version:get -p ios)
-outputAndroid=$(eas build:version:get -p android)
-BSKY_IOS_BUILD_NUMBER=${outputIos#*buildNumber - }
-BSKY_ANDROID_VERSION_CODE=${outputAndroid#*versionCode - }
+# Build numbers already present in the environment take precedence over the
+# global EAS counters. Production OTA deploys rely on this to target the
+# specific native build they are for, since the counters advance with every
+# testflight build.
+if [ -z "${BSKY_IOS_BUILD_NUMBER:-}" ]; then
+  outputIos=$(eas build:version:get -p ios)
+  BSKY_IOS_BUILD_NUMBER=${outputIos#*buildNumber - }
+fi
 
-bash -c "BSKY_IOS_BUILD_NUMBER=$BSKY_IOS_BUILD_NUMBER BSKY_ANDROID_VERSION_CODE=$BSKY_ANDROID_VERSION_CODE $*"
+if [ -z "${BSKY_ANDROID_VERSION_CODE:-}" ]; then
+  outputAndroid=$(eas build:version:get -p android)
+  BSKY_ANDROID_VERSION_CODE=${outputAndroid#*versionCode - }
+fi
+
+export BSKY_IOS_BUILD_NUMBER BSKY_ANDROID_VERSION_CODE
+exec "$@"