Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, #2305

Closed
Aris-ngoy opened this issue Mar 28, 2024 · 61 comments
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@Aris-ngoy
Copy link

Build/Submit details page URL

No response

Summary

eas-cli/7.6.2 darwin-x64 node-v18.19.1

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 3)

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 2)

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 1)

✖ Failed to sync capability identifiers app.abela
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
Error: build command failed.

Managed or bare?

Managed

Environment

expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.4
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.19.1 - ~/.nvm/versions/node/v18.19.1/bin/node
npm: 10.2.4 - ~/.nvm/versions/node/v18.19.1/bin/npm
Watchman: 2024.01.22.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.15.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4
IDEs:
Xcode: 15.3/15E204a - /usr/bin/xcodebuild
npmPackages:
expo: ~50.0.13 => 50.0.13
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.73.5 => 0.73.5
react-native-web: ~0.19.6 => 0.19.10
npmGlobalPackages:
eas-cli: 7.6.2
Expo Workflow: bare

Error output

✔ Synced capabilities: No updates

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 3)

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 2)

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 1)

✖ Failed to sync capability identifiers app.abela
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
Error: build command failed.

Reproducible demo or steps to reproduce from a blank project

eas build -p ios production

@Aris-ngoy Aris-ngoy added the needs review Issue is ready to be reviewed by a maintainer label Mar 28, 2024
@heyjamesknight
Copy link

Same issue.

1 similar comment
@deho0701
Copy link

deho0701 commented Apr 1, 2024

Same issue.

@lumamontes
Copy link

I was having the same issue but updating eas-cli and then building again worked for me:

npm install -g eas-cli

@ThangNV1205
Copy link

I also encountered a similar error even when using the latest version of eas-cli globally. I removed it globally and installed it directly into the project, and the build went smoothly.

@impe93
Copy link

impe93 commented May 9, 2024

Same error here, I tried what @lumamontes said but I still get the error. One thing to notice is that when I'm bumping up the node version from 16 to 18.20.2, I get the connection error, but if I downgrade to version 16 again, everything works like a charm. I don't see how those 2 things are connected but that's what i've noticed. Other than that I HAVE TO switch to node version 18 because the latest plugin "expo-privacy-manifest-polyfill-plugin" to fix stuff on iOS env privacy need a function that seems to be only present on node 18. I'm a bit scared about this because I've to deploy an update for Monday lol

@bportman
Copy link

Event though I already had eas-cli installed globally and things were working fine for a while, running npm install -g eas-cli fixed this for me when the error started popping up.

@Nikita-Shuminskiy
Copy link

use npx (npx eas build --profile) instead of eas(eas build --profile) it worked

@Heverson
Copy link

Heverson commented Jun 1, 2024

I was having the same issue but updating eas-cli and then building again worked for me:

npm install -g eas-cli

Worked for me, thanks!

@rcarter
Copy link

rcarter commented Jun 13, 2024

Receiving this after updating eas-cli to v10.0.0 today. Reverted to v9.2.0 and all worked fine.

@steviec
Copy link

steviec commented Jun 19, 2024

Getting this same issue, none of the above solutions fixed it for me :(. I'm getting it only when attempting an eas build with a particular profile; all the other ones work fine. There's nothing different, AFAICT, about this one.

@nitishanand99
Copy link

idk how but I did these steps and it worked for me,

  • downgrade to the last but one version of eas-cli sudo npm install -g [email protected]
  • sudo npm i
  • upgraded to the latest again sudo npm i -g eas-cli
  • then used sudo for eas build sudo eas build -p ios -e development
    the last step probably did the trick.

@NandoGoulartt
Copy link

NandoGoulartt commented Jul 1, 2024

npm install -g eas-cli

Funcionou para mim, obrigado!

@opmat
Copy link

opmat commented Jul 11, 2024

I experienced the same issue after I upgraded to [email protected] today. I had to downgrade to version 10.0.0 before the build was successful.

The exact error I got was

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 3)


Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 2)


Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 1)

✖ Failed to sync capability identifiers ng.fob.mobile
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
    Error: build command failed.

My environment info is below

expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 14.2.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 18.20.3 - ~/.nvm/versions/node/v18.20.3/bin/node
      Yarn: 1.22.22 - ~/.yarn/bin/yarn
      npm: 10.7.0 - ~/.nvm/versions/node/v18.20.3/bin/npm
    Managers:
      CocoaPods: 1.11.3 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
    IDEs:
      Android Studio: 2021.1 AI-211.7628.21.2111.8193401
      Xcode: 15.4/15F31d - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ^19.0.0 => 19.0.1 
      expo: ^50.0.19 => 50.0.19 
      react: 18.2.0 => 18.2.0 
      react-dom: 18.2.0 => 18.2.0 
      react-native: 0.73.6 => 0.73.6 
      react-native-web: ~0.19.6 => 0.19.12 
    npmGlobalPackages:
      eas-cli: 10.1.1
    Expo Workflow: managed

@MariuzM
Copy link

MariuzM commented Jul 15, 2024

One second it was building locally fine and next started this happening...

Tried 10.0.0 same issue

@szdziedzic
Copy link
Member

Hi, all!

It seems possible that Apple is doing some maintenance on their Developer Portal again 🤔

At what point of running the eas build command did it fail for you?

I believe that it is possible to know the exact request that failed if you use the EXPO_APP_STORE_DEBUG=1 EXPO_DEBUG=1 flags when running the eas build command. It would be helpful information for me because I'm having a hard time replicating the issue at the moment on my machine.

A few months ago in version 7.6.0 we added a logic to switch between the developer.apple.com and developer-mdn.apple.com domains when one of them is under the maintenance, but this error seems to not be caught by this logic. I will try to make it better by switching the domain on every internal server error we see because I believe it seems to work.

@szdziedzic
Copy link
Member

I just released the new 10.2.0 EAS CLI version that will try to resolve the issue by switching between the developer.apple.com and developer-mdn.apple.com domains on every internal server error.

Please, let me know if it helps in your case.

@gchen1196
Copy link

PATCH https://developer.apple.com/services-account/v1/bundleIds/
Error: Request failed with status code 501 (PATCH https://developer.apple.com/services-account/v1/bundleIds/)

Internal Server Error: 'd', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later'. Retrying after 3 seconds (remaining: 3)

PATCH https://developer-mdn.apple.com/services-account/v1/bundleIds/
Error: Request failed with status code 503 (PATCH https://developer-mdn.apple.com/services-account/v1/bundleIds/)
-- App Store Connect Error JSON --
{
"errors": [
{
"id": "610b951e-a7cb-925ebda53f72",
"status": "503",
"code": "SERVICE_NOTACTIVE",
"title": "This request can not be processed right now",
"resultCode": 10405,
"detail": "Service not available because of maintenance activities, please try again after some time."
}
]
}
-- End ASC Error JSON --

@tmw102
Copy link

tmw102 commented Jul 23, 2024

I had an agreement outstanding in App Store Connect. Once I had signed it, this error went away.

@rgomezp
Copy link

rgomezp commented Aug 27, 2024

I had removed my app from review so it was marked as "developer rejected". Once I removed the old build from the release, it started working

@Seanmclem
Copy link

I was already using npx so no global install issue. I logged into the app store connect website to make sure my account/app was in good standing. It was. So I tried npx eas build again, and it just worked. So try that and try again before spending too much time searching.

@LKL2017
Copy link

LKL2017 commented Sep 19, 2024

any updates here? I'm using eas-cli/12.4.1 and node-v20.13.1, meet the same issue

@saurabhbhatia
Copy link

saurabhbhatia commented Oct 18, 2024

Same problem, eas-cli@latest and node v22.5.1. I've tried to update the eas-cli a bunch of times and also used npx to run the command.

@noahkurz
Copy link

Same issue here as @saurabhbhatia

@mcr5fh
Copy link

mcr5fh commented Oct 19, 2024

Seeing 500s as well, and the global install did not help, nor did a downgrade, even to v12.5.0. My app store connect looks to be in good standing as well. Anyone have any luck here?

Example command:

EXPO_APP_STORE_DEBUG=1 EXPO_DEBUG=1 EAS_PWD=$PWD EAS_LOCAL_BUILD_SKIP_CLEANUP=1 npx eas build --profile production --platform ios --local

And this is the stack trace

⠇ Logging in...Error: Request failed with status code 503 (POST https://idmsa.apple.com/appleauth/auth/signin)
✖ Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
d [Error]: Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
    at t.getAppleResponseError (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:828021)
    at block (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:834431)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async O (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:834956)
    at async T (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:833825)
    at async t.requestAsync (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:836214)
    at async /path/to/project/node_modules/@expo/apple-utils/build/index.js:1:704687
    at async w (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:703817)
    at async Object.S [as loginWithUserCredentialsAsync] (/path/to/project/node_modules/@expo/apple-utils/build/index.js:1:703396)
    at async loginWithUserCredentialsAsync (/path/to/project/node_modules/eas-cli/build/credentials/ios/appstore/authenticate.js:84:24) {
  response: {
    status: 503,
    statusText: 'Service Temporarily Unavailable',
    headers: {
      server: 'Apple',
      date: 'Sat, 19 Oct 2024 00:57:55 GMT',
      'content-type': 'text/html',
      'content-length': '190',
      connection: 'keep-alive'
    },
    config: {
      url: 'https://idmsa.apple.com/appleauth/auth/signin',
      method: 'post',
      data: '{"accountName":"REDACTED","password":"REDACTED","rememberMe":true}',
      headers: [Object],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 0,
      withCredentials: true,
      adapter: [Function (anonymous)],
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      maxBodyLength: -1,
      jar: [M],
      maxRedirects: 0,
      baseURL: 'https://idmsa.apple.com/appleauth',
      validateStatus: [Function: validateStatus]
    },
    request: ClientRequest {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      outputData: [],
      outputSize: 0,
      writable: true,
      destroyed: true,
      _last: false,
      chunkedEncoding: false,
      shouldKeepAlive: true,
      maxRequestsOnConnectionReached: false,
      _defaultKeepAlive: true,
      useChunkedEncodingByDefault: true,
      sendDate: false,
      _removedConnection: false,
      _removedContLen: false,
      _removedTE: false,
      strictContentLength: false,
      _contentLength: 116,
      _hasBody: true,
      _trailer: '',
      finished: true,
      _headerSent: true,
      _closed: true,
      socket: [TLSSocket],
      _header: 'POST /appleauth/auth/signin HTTP/1.1\r\n' +
        'Accept: application/json, text/javascript\r\n' +
        'Content-Type: application/json\r\n' +
        'User-Agent: Xcode\r\n' +
        'X-Xcode-Version: 7.0 (7A120f)\r\n' +
        'X-Requested-With: XMLHttpRequest\r\n' +
        'X-Apple-Widget-Key: REDACTED\r\n' +
        'X-APPLE-HC: 1:12:20241019005755:REDACTED::16739\r\n' +
        'Cookie: myacinfo=REDACTED' +
        'Content-Length: 116\r\n' +
        'Host: idmsa.apple.com\r\n' +
        'Connection: keep-alive\r\n' +
        '\r\n',
      _keepAliveTimeout: 0,
      _onPendingData: [Function: nop],
      agent: [Agent],
      socketPath: undefined,
      method: 'POST',
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      joinDuplicateHeaders: undefined,
      path: '/appleauth/auth/signin',
      _ended: true,
      res: [IncomingMessage],
      aborted: false,
      timeoutCb: null,
      upgradeOrConnect: false,
      parser: null,
      maxHeadersCount: null,
      reusedSocket: true,
      host: 'idmsa.apple.com',
      protocol: 'https:',
      [Symbol(shapeMode)]: false,
      [Symbol(kCapture)]: false,
      [Symbol(kBytesWritten)]: 0,
      [Symbol(kNeedDrain)]: false,
      [Symbol(corked)]: 0,
      [Symbol(kOutHeaders)]: [Object: null prototype],
      [Symbol(errored)]: null,
      [Symbol(kHighWaterMark)]: 16384,
      [Symbol(kRejectNonStandardBodyWrites)]: false,
      [Symbol(kUniqueHeaders)]: null
    },
    data: '<html>\r\n' +
      '<head><title>503 Service Temporarily Unavailable</title></head>\r\n' +
      '<body>\r\n' +
      '<center><h1>503 Service Temporarily Unavailable</h1></center>\r\n' +
      '<hr><center>Apple</center>\r\n' +
      '</body>\r\n' +
      '</html>\r\n'
  }
}

@superunrelated
Copy link

Same here. No mention about an Apple outage here though: https://developer.apple.com/system-status/

@SirFroweey
Copy link

Same issue

@K-E-L
Copy link

K-E-L commented Oct 19, 2024

Same, tried downgrading eas-cli to 12.5.1, tried upgrading to Node 22, running out of ideas

@mcr5fh
Copy link

mcr5fh commented Oct 19, 2024

FYI, I just added --non-interactive and was able to successfully build and upload to ASC

Full command that worked: EXPO_APP_STORE_DEBUG=1 EXPO_DEBUG=1 EAS_PWD=$PWD EAS_LOCAL_BUILD_SKIP_CLEANUP=1 npx eas build --profile production --non-interactive --platform ios --local

Saw the idea here: #2497 (comment)

@lperotti399
Copy link

seems like others are facing the same issue in this thread https://forums.developer.apple.com/forums/thread/749354

@K-E-L
Copy link

K-E-L commented Oct 19, 2024

I downloaded the build from the Expo site, then uploaded it through the Transporter app on the Mac App Store, and it worked! Now I am able to see it in TestFlight.

@lperotti399
Copy link

I was able to get the eas build and eas submit to work using eas build --non-interactive --platform ios --auto-submit

Prior to running this I had to set up my production profile with the proper submit information in my eas.json file. That documentation is here https://docs.expo.dev/submit/eas-json/

@ESarcomere
Copy link

I am using a windows laptop. I get this error when I run this : npx eas build --profile production --non-interactive --platform ios
Distribution Certificate is not validated for non-interactive builds.
Failed to set up credentials.
Credentials are not set up. Run this command again in interactive mode.

And when I try: npx eas build --profile production --platform ios
I get :
Error: Request failed with status code 503 (POST https://idmsa.apple.com/appleauth/auth/signin)
× Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
...
status: 503,
statusText: 'Service Temporarily Unavailable',

Has anyone fixed this? Can I even build ios apps from windows laptops?

@sudhakarAndroid
Copy link

I'm also getting same error.

× Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
Error: build command failed.

@alessiapacca
Copy link

@lperotti399 great solution, worked for me!!

@nars-bramble
Copy link

@lperotti399
getting the below error when using the "--non-interactive" command

Failed to set up credentials.
Credentials are not set up. Run this command again in interactive mode.
Error: build command failed.

@saurabhbhatia
Copy link

saurabhbhatia commented Oct 19, 2024

Looks like this is now acknowledged by team expo as service degradation https://status.expo.dev

@devsphere-apps
Copy link

What are the methods not worked for me

  • npm install -g eas-cli
  • npm uninstall -g eas-cli expo-cli
  • npm install -g eas-cli
  • npm install -g eas-cli@latest
  • eas logout
  • eas login
  • npm cache clean
  • npm cache clean --force
  • removed my app from review so it was marked as "developer rejected".

Worked for me

  • eas build --platform ios --non-interactive // --non-interactive worked
  • eas submit --platform ios

@alessiapacca
Copy link

alessiapacca commented Oct 19, 2024

@nars-bramble did you setup your eas.json? should include:

"submit": {
    "production": {
      "ios": {
        "appleId": "yourappleid",
        "ascAppId": "yourappid",
        "appleTeamId": "yourteamid"
      }
    }
  }

@AyoCodess
Copy link

FYI, I just added --non-interactive and was able to successfully build and upload to ASC

Full command that worked: EXPO_APP_STORE_DEBUG=1 EXPO_DEBUG=1 EAS_PWD=$PWD EAS_LOCAL_BUILD_SKIP_CLEANUP=1 npx eas build --profile production --non-interactive --platform ios --local

Saw the idea here: #2497 (comment)

this worked, but i don't like it.

@nars-bramble
Copy link

@alessiapacca Yes, updated the eas file before running the command and got the following error.

Failed to set up credentials.
Credentials are not set up. Run this command again in interactive mode.
Error: build command failed.

@AbdessamadAe
Copy link

AbdessamadAe commented Oct 19, 2024

Running eas build in debug mode throws back the error:

Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later

with the following response:

response: {
    status: 503,
    statusText: 'Service Temporarily Unavailable',
    headers: {
      server: 'Apple',
      date: 'Sat, 19 Oct 2024 18:28:31 GMT',
      'content-type': 'text/html',
      'content-length': '190',
      connection: 'keep-alive'
    }

@AbdessamadAe
Copy link

Issue was fixed here: #2639
Just upgrade to latest eas-cli

@nars-bramble
Copy link

Issue got resolved once I updated the cli to new version. Thanks guys!

@sam-abdul
Copy link

Try npm install -g eas-cli@latest if npm install -g eas-cli isnt working

@pH-7
Copy link

pH-7 commented Oct 20, 2024

Confirming that updating eas to the latest version would do it.

@LucasParra
Copy link

Confirming that installing the last version of eas-cli fixes the problem, I use node18 just for reference

@Thxmxs
Copy link

Thxmxs commented Oct 21, 2024

npm install -g eas-cli worked for me

im using:
node: 20.14.0
"expo": "~51.0.31"

@forestDev1212
Copy link

I was having the same issue but updating eas-cli and then building again worked for me:

npm install -g eas-cli

It works for me too.
Thank you.

@navigiljshuusko
Copy link

npm install -g eas-cli worked for me too

Thank you.

@saurabhbhatia
Copy link

Forgot to confirm, this worked perfectly. Thank you so much for such quick turnaround.

@bx-hamza
Copy link

For the people for whom upgrading eas-cli didn't solve the issue, running 'sudo' with your build will allow the credentials update to occur, as per nitishanand99 instructions.

idk how but I did these steps and it worked for me,

  • downgrade to the last but one version of eas-cli sudo npm install -g [email protected]
  • sudo npm i
  • upgraded to the latest again sudo npm i -g eas-cli
  • then used sudo for eas build sudo eas build -p ios -e development
    the last step probably did the trick.

@JoPoTe
Copy link

JoPoTe commented Oct 30, 2024

I was having the same issue but updating eas-cli and then building again worked for me:

npm install -g eas-cli

Worked like a charm :) thank you!

@GregBaLpro
Copy link

Confirming here npm install -g eas-cli worked for me too.

@BilegtGG
Copy link

BilegtGG commented Nov 6, 2024

guys keep calm goto https://appstoreconnect.apple.com/ accept new terms then im ok

@VadymBezsmertnyi
Copy link

The change in the eas.json version to:

"cli": {
    "version": ">= 10.0.2"
}

and the addition of:

"submit": {
    "production": {
        "ios": {
            "ascAppId": "*******"
        }
    }
}

helped me solve the issue.

@Palvaran
Copy link

Palvaran commented Dec 5, 2024

VadymBezsmertnyi, thanks. That helped me and I was able to submit.

@spsaucier
Copy link

If you have phone call as the 2FA method, you may receive this error. See #879 for more info.

I had to switch to a different Apple ID to get it to work at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests