expo build:ios returns: Apple 403 detected - Access forbidden

expo diagnostics:

  Expo CLI 4.11.0 environment info:
    System:
      OS: macOS 11.5
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
      Yarn: 1.22.10 - ~/.nvm/versions/node/v16.0.0/bin/yarn
      npm: 7.20.5 - ~/.nvm/versions/node/v16.0.0/bin/npm
      Watchman: 4.9.0 - /opt/homebrew/bin/watchman
    IDEs:
      Xcode: /undefined - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ~0.12.68 => 0.12.82
      expo: ^41.0.1 => 41.0.1
      react: 16.13.1 => 16.13.1
      react-dom: 16.13.1 => 16.13.1
      react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz => 0.63.2
      react-native-web: ~0.13.12 => 0.13.18
    npmGlobalPackages:
      expo-cli: 4.11.0
    Expo Workflow: managed

When running expo build:ios -t archive, I get:

Checking if there is a build in progress...

Accessing credentials for ********* in project ***********
✔ Do you have access to the Apple account that will be used for submitting this app to the App Store? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: … ******@mac.com
› Using password for ******@mac.com from your local Keychain
  Learn more.
✔ Logged in, verify your Apple account to continue
Two-factor Authentication (6 digit code) is enabled for ******@mac.com. Learn more.

✔ How do you want to validate your account? … device / sms
✔ Please enter the 6 digit code … *******
✔ Valid code
✔ Logged in and verified
› Team ***************
› Provider ******************

Network Timeout: 'AccessForbiddenError', 'Apple 403 detected - Access forbidden'. Retrying after 3 seconds (remaining: 3)


Network Timeout: 'AccessForbiddenError', 'Apple 403 detected - Access forbidden'. Retrying after 3 seconds (remaining: 2)


Network Timeout: 'AccessForbiddenError', 'Apple 403 detected - Access forbidden'. Retrying after 3 seconds (remaining: 1)

etc.

So first it logs in (it says Logged in and verified) and then gives a forbidden error.

Any idea?

Never mind, I had to accept a new policy by Apple on the developer website.

1 Like

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.