eas-cli login credentials prompt is autofilled with a full shell command string - unable to fix

### Build/Submit details page URL

_No response_

### Summary

I’m hitting a weird eas-cli issue and would love any help.

When I try to build for iOS, the **Apple ID login credentials prompt is autofilled with a full shell command string** is autofilled by a previously ran:

`Apple ID: rm -rf ~/.eas/credentials && FASTLANE_USER=myemail@email.com ...`

It no longer asks for proper credentials — just injects that which blocks me from being able to login. Happens even in fresh terminals, even after nuking configs, uninstalling, etc., any new build still autofills with that instead of prompting for a real Apple ID. Totally blocks credential setup.

Tried a ton, still stuck — here’s what I’ve done so far:

Removed EAS credentials: rm -rf ~/.eas/credentials,
Removed EAS directory: rm -rf ~/.eas,
Removed Fastlane credentials: rm -rf ~/.fastlane,
Cleared EAS CLI cache: rm -rf ~/Library/Caches/eas-cli,
Uninstalled & reinstalled eas-cli: npm uninstall -g eas-cli && npm install -g eas-cli,
Ran with env vars: FASTLANE_USER=... npx eas-cli build,
Used --non-interactive and --no-credentials flags,
Cleared shell history completely,
Tried fresh terminals & new shell sessions,
Checked/removed keychain items,
Verified no aliases: alias | grep eas,
Verified shell configs — no exported vars,
Explicitly unset: unset FASTLANE_USER FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD

### Managed or bare?

managed

### Environment

expo-env-info 1.3.3 environment info:
System:
OS: macOS 14.6.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.14.0 - /usr/local/bin/node
npm: 11.3.0 - /usr/local/bin/npm
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
IDEs:
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
npmPackages:
expo: ^53.0.9 => 53.0.9
react: 19.0.0 => 19.0.0
react-native: 0.79.2 => 0.79.2
react-navigation: ^5.0.0 => 5.0.0
npmGlobalPackages:
eas-cli: 16.6.1
Expo Workflow: managed

>

env: load .env
env: export SUPABASE_URL SUPABASE_ANON_KEY
13/15 checks passed. 2 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

✖ Check dependencies for packages that should not be installed directly
The package "@types/react-native" should not be installed directly in your project, as types are included with the "react-native" package.
Advice:
Remove these packages from your package.json.

✖ Validate packages against React Native Directory package metadata
The following issues were found when validating your dependencies against React Native Directory:
Untested on New Architecture: react-native-autogrow-textinput, react-native-keyboard-aware-scroll-view
Unmaintained: react-native-autogrow-textinput, react-native-keyboard-aware-scroll-view, react-native-switch
No metadata available: @babel/plugin-proposal-optional-chaining, expo-checkbox, phosphor-react-native, react-native-feather, react-native-vector-icons, react-navigation
Advice:
Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

2 checks failed, indicating possible issues with the project.

### Error output

_No response_

### Reproducible demo or steps to reproduce from a blank project

I have no idea how to reproduce the issue...