Trying to whitelist expo updates url for sim provider but cant?

Expo Development Tools
1

We have these sim cards that currently blacklist all websites (this is because we give out devices + sim cards and want to ensure data is only used for our app). We’ve added in expo updates, and im trying to find the right url to whitelist, but expo updates are not coming through!

expo.dev, exp.host are what i’ve tried but neither allow our app to check for updates with the sim.

Do you guys know what else i need to whitelist? thanks!

code for expo updates config suggests exp.host is the correct one but it is not working:

android:name=“expo.modules.updates.EXPO_UPDATE_URL”
android:value=“https://exp.host/[redacted]/[redacted]” />

2

Hi @hcarney

Just a guess, but also try expo.io. I doubt expo.fyi would be needed.

I think the updates themselves come from an S3 bucket, though, so it might not be enough to whitelist the Expo domains.

4

I did add expo.io and exp.direct today but that didn’t work either, do you know if I can whitelist all of s3/amazon? What would be the start of the domain for that? s3.amazonaws.com i suppose? Edit: whitelisting that didnt work :confused:

5

I’m struggling to get the manifest.

Something like this used to work:

curl -L -i \
    -H 'Exponent-SDK-Version: 35.0.0,36.0.0,34.0.0,33.0.0' \
    -H 'Exponent-Platform: android' \
    -H 'Exponent-Version: 2.14.0' \
    -H 'Accept: application/expo+json,application/json' \
    -H 'Expo-Api-Version: 1' \
    -H 'Expo-Client-Environment: EXPO_DEVICE' \
    -H 'Expo-Session: {"id":"aaabbbcc-1234-5678-9abc-dddeeefff000","version":1,"expires_at":1893456000000}' \
    -H 'Exponent-Accept-Signature: true' \
    -H 'Expo-JSON-Error: true' \
    -H 'User-Agent: okhttp/3.12.1' \
    'http://exp.host/@user/slug'

but if I try some variation on that now I get an error about the update not being available for that platform “android” and release channel “default” or something like that.

It looks like more modern headers are as follows:

But that didn’t work for me either.

If you can figure out how to make the request to get the manifest, you’ll see several URLs in there, in particular bundleUrl and URLs for splash screen and app icon.

Also, here are some more domains:

EDIT:
Maybe this stuff will help to figure out how to fetch the manifest:

6

Ah mate absolute life saver - this worked! In the end I whitelisted (on top of the ones previously posted)

d1wp6m56sqw74a.cloudfront.net
classic-assets.eascdn.net

Seems it was likely that the images werent coming through because they get stored in two separate domains…and it was failing expo updates

Thanks for your help!

1 Like
7

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