Travis: exp publish

#1

I’m trying to get Travis to publish my Expo app. Unfortunately, I ran into the same “socket hang up” issues as Error when running exp publish: socket hang up. The workaround mentioned in that issue helped, i.e. setting

    "packagerOpts": {
      "nonPersistent": true
    }

helped. On the other hand, this lead to issues in local development (no live reload), which makes sense, since this deactivates the watcher according to the issue above. Is there some way to use a different config on Travis than for development? I probably could change my deploy script so that it modifies app.json beforehand, but that doesn’t seem right.

Thanks in advance for any pointers :slight_smile: