Since last evening I’ve been hitting this error when trying to run EXP_DEBUG=true exp build:ios --release-channel prod (note I have axios-debug-logging installed, was hoping to see which URL was causing the 404 error):
? How would you like to upload your credentials?
Expo handles all credentials, you can still provide overrides
We need your Apple ID/password to manage certificates and
provisioning profiles from your Apple Developer account.
Note: Expo does not keep your Apple ID or your Apple password.
? What's your Apple ID? REDACTED
? Password? [hidden]
[14:52:09] Validating Credentials...
To run _spaceship_ through a local proxy, use SPACESHIP_DEBUG
[14:52:11] You have 2 teams
1) REDACTED
2) REDACTED
? Which Team ID to use? 2) REDACTED
To run _spaceship_ through a local proxy, use SPACESHIP_DEBUG
? Will you provide your own Distribution Certificate? Let Expo handle the process
? Will you provide your own Push Certificate? Let Expo handle the process
? Would you like to reuse Distribution Certificate from another app? Used in apps: REDACTED
⠙ Now producing files for pushCertTo run _spaceship_ through a local proxy, use SPACESHIP_DEBUG
⠙ Now producing files for provisioningProfileTo run _spaceship_ through a local proxy, use SPACESHIP_DEBUG
[14:52:26] Error while gathering & validating credentials
[14:52:26] Error: Request failed with status code 404
[14:52:26] Request failed with status code 404
[14:52:26] Error: Request failed with status code 404
at createError (/usr/local/lib/node_modules/exp/node_modules/axios/lib/core/createError.js:16:15)
at settle (/usr/local/lib/node_modules/exp/node_modules/axios/lib/core/settle.js:18:12)
at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/exp/node_modules/axios/lib/adapters/http.js:191:11)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1081:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
Hi, we’re looking into this. It looks like there are some DB entries that fail some invariants. We are adding some more diagnostics to figure out the root cause right now.
@drive.ai
Hello,
I just deployed a fix, which should probably let you build your app again.
I’m curious about one thing. Did you change bundle_identifier in your app.json? I guess this was causing the problem on our servers.
Sorry for the trouble.
@ide: thanks so much for expediting the fix to this issue, it is very much appreciated! I am indeed back to building successfully.
I had been building different release channels (test, prod) with different bundle IDs, but the build that was failing for me was our main bundle ID (ai.drive.app) which I had built many times successfully before. Maybe it was that anyway?
Either way, thank you again very much. Cheers Expo team indeed!!
Yes, we believe the issue matches the symptoms you were seeing. We had a database constraint that didn’t allow for changing native bundle IDs while keeping the same Expo project name. That constraint now allows for changes to bundle IDs.