I figured my issues out. Basically I had a docker containing that was running on port 80 which was causing the packager to report that one is already running.
Is this causing my issue?
NOTES:
I also get the warning on my local machine but the publish does start afterwards with Starting Metro Bundler on port 19001. …
Hey! Could you try passing --max-workers 1 to exp publish? It limits the number of workers used by Metro bundler, which is known to cause issues with some CI servers that report a higher number of CPU cores than the build processes actually have available.
hi @jdruwe, the next step in the publish process would be 11:46:46 [exp] Starting Metro Bundler on port 19001.
Maybe check that theres nothing on port 19001?