We’re attempting to use detached ExpoKit and host our own manifest and JS bundle. I can look at the manifest in development by manually switching exp:// in the URL to http://:
$ curl localhost:19000 -v
* Rebuilt URL to: localhost:19000/
* Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 19000 (#0)
> GET / HTTP/1.1
> Host: localhost:19000
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Exponent-Server: {"host":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx" ...}
< Content-Type: text/html; charset=utf-8
< Content-Length: 1586
< ETag: W/"632-M0/D5QInFBJWDqzwMmv3QkzQXLY"
< Date: Wed, 08 Aug 2018 15:17:58 GMT
< Connection: keep-alive
<
* Connection #0 to host localhost left intact
{"name":"project","slug":"project", ....
When I look in ./ios/project/Supporting/EXShell.plist for the detached build, I see the following for the manifest information:
<key>manifestUrl</key>
<string>exp://exp.host/@company/project</string>
but when I attempt to cURL this to obtain the production manifest, I’m seeing a redirect to the project’s Expo landing page:
$ curl https://exp.host/@company/project -v
* Trying 35.202.142.166...
* TCP_NODELAY set
* Connected to exp.host (35.202.142.166) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: expo.io
* Server certificate: Let's Encrypt Authority X3
* Server certificate: DST Root CA X3
> GET /@company/project HTTP/1.1
> Host: exp.host
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.13.12
< Date: Wed, 08 Aug 2018 15:15:52 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 93
< Connection: keep-alive
< Vary: Accept-Encoding, Origin
< Strict-Transport-Security: max-age=15724800
< Location: //expo.io/@company/project
<
* Connection #0 to host exp.host left intact
Is there a way to obtain the Expo hosted manifest file to duplicate it on our own CDN?