Always getting 404 when trying to eject the project.

[becavalier]

As titled.

  Expo CLI 3.11.7 environment info:
    System:
      OS: macOS 10.14.6
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.16.0 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.12.0 - /usr/local/bin/npm
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5692245
      Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
    npmGlobalPackages:
      expo-cli: 3.11.7

[wodin]

Does expo login work for you? If so, does it help to do that before trying to eject?

The ejection works for me, although I get some strange messages about CGColor:

$ expo eject
Your git working tree is clean
To revert the changes after this command completes, you can run the following:
  git clean --force && git reset --hard

? How would you like to eject your app?
  Read more: https://docs.expo.io/versions/latest/expokit/eject/ ExpoKit
? What would you like your iOS bundle identifier to be? org.example.test-app
<CGColor 0x7fd286702650> [<CG<CCoGlCoorlSorp a0cxe7 fcda01x170f2db25806>7 0[2<3CbG0C>o l(okrCSGpCaocleo r0Sxp7afccedDae1v1i0c2e8RbG0B>) ]( k(C G0C o0l o0r S1p a)ce
DeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7f9c7750b230> [<CGColorSpace 0x7f9c7750af90> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7f9a67903620> [<CGColorSpace 0x7f9a67903380> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fae52200fe0> [<CGColorSpace 0x7fae52200d40> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fbce8300860> [<CGColorSpace 0x7fbce83007a0> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fbb29003e40> [<CGColorSpace 0x7fbb29003bc0> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fa815504850> [<CGColorSpace 0x7fa8155045b0> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fa1ad5033f0> [<CGColorSpace 0x7fa1ad503150> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fcde0b02140> [<CGColorSpace 0x7fcde0b04d20> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fb74a205340> [<CGColorSpace 0x7fb74a2050a0> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7f85cb70a1e0> [<CGColorSpace 0x7f85cb709f10> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
? What would you like your Android package name to be? org.example.test_app
<CGColor 0x7ff80540f390> [<CGColorSpace 0x7ff80540f0f0> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fc533503ff0> [<CGColorSpace 0x7fc533503f30> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7ff609609fa0> [<CGColorSpace 0x7ff609609d00> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
<CGColor 0x7fc4d1102de0> [<CGColorSpace 0x7fc4d1102b40> (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
Ejected successfully!

expo was already logged in before I ejected.

By the way, EkpoKit is not really encouraged anymore:

Migrating from ExpoKit

Historically when you have run expo eject , you’d end up with an ExpoKit project. ExpoKit is a large library that includes the entire Expo SDK, and it leaves you in this place where you’re not quite writing a vanilla React Native project and you’re not quite using the Expo managed workflow. At Expo we decided to move away from the ExpoKit architecture towards the “bare workflow” model, where your project is a “bare” or “vanilla” React Native project with only the pieces of the Expo SDK that you need for your project, no more. We will continue to support ExpoKit until the bare workflow has no limitations relative to ExpoKit, but we aren’t quite there yet.

So if you can use the Bare workflow instead that might be better. The Expo team is working to remove the remaining limitations of the Bare workflow:

Finish ExpoKit module extraction