Error: Experience not published

Hi devs! Today I had a problem when compiling my app. After pointing my keystore, the expo show me this messages:
No assets changed, skipped.
Processing asset bundle patterns:

  • /Users/vinicius/Sites/plom-beta/**/*
    Uploading JavaScript bundles
    Publish complete

The manifest URL is: (​​). Learn more. (​​)
The project page is: Expo (​​). Learn more. (​​)
› Closing Expo server
› Stopping Metro bundler
Checking if this build already exists…

It’s ok, but after this, expo show an error:
Experience not published.

Anybody knows whats the problem?

Sorry about my english. I don’t type very well lolo


Edmar from Brazil.


Expo CLI 3.22.3 environment info:
OS: macOS Mojave 10.14.6
Shell: 3.2.57 - /bin/bash
Node: 12.18.2 - ~/.nvm/versions/node/v12.18.2/bin/node
Yarn: 1.22.5 - /usr/local/bin/yarn
npm: 6.14.7 - ~/.nvm/versions/node/v12.18.2/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild

hi! it’s possible this was due to something on our end (since there are two reports of it), but just to cover our bases could you upgrade to the most recent expo-cli version?

also @edmardelima it looks like you might be using team features, but this publish is going through as your own. If you’re trying to build as part of a team, remember to set the owner field in app.json

Just happened to me as well, expo-cli version 3.28.1

We just pushed a fix out, you should be able to publish and build without that issue anymore (the fix was server-side, so there’s no need to upgrade expo-cli )

also with me, expo-cli version 3.28.2

Thanks @charliecruzan!!! It’s building! I will upgrade my expo-cli, but it did with version 3.22.


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