question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Experience \"@[secure]/expomultiscreenstarter\" for platform \"[secure]\" and release channel \"default\" does not exist or is not published.

See original GitHub issue

New Issue Checklist

  • Updated turtle-cli to the latest version (yarn global add turtle-cli or npm install --global turtle-cli).
  • I read the Contribution Guidelines.
  • I read docs.expo.io (Managed Workflow > Distributing Your App).
  • I searched for existing GitHub issues.
  • I enclosed the complete output when running turtle, including the stack trace and command used.

Issue Description

I write a travis ci config file according https://github.com/expo/turtle-cli-example/blob/master/.travis.yml, but when the ci execute turtle build:android --keystore-path ./expo-project.jks --keystore-alias $EXPO_ANDROID_KEYSTORE_ALIAS --type apk -o $ARTIFACT_PATH, it always gave me turtle[5266] ERROR: { StatusCodeError: 404 - "Experience \"@[secure]/expomultiscreenstarter\" for platform \"[secure]\" and release channel \"default\" does not exist or is not published." error.

more detail can be found on https://travis-ci.org/liudonghua123/expo-multi-screen-starter/jobs/591506731

I can confirm that environment variables are correct and https://expo.io/@liudonghua/expomultiscreenstarter is reachable.

Command executed

see the travis log above.

Complete output when running turtle, including the stack trace and command used

see the travis log above.

Environment

see the travis log above.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

4reactions
gang544043963commented, Aug 4, 2020

Yep, I met the same error. It is an expo account error. EXPO_USERNAME should be “[username]”, not “[email]”. (If you use CI Build)

0reactions
trajanocommented, Oct 30, 2020

This wouldn’t have been an issue if Turtle supported EXPO_TOKEN

Read more comments on GitHub >

github_iconTop Results From Across the Web

Release channels
Use release channels in Expo to send out different versions of your ... If you do not specify a release channel, you will...
Read more >
how to list all EXPO release-channel? - react native
You can see everything that you've published with expo publish:history. Also you can filter by platform: expo publish:history --platform ios.
Read more >
Build Standalone Expo .apk and .ipa with Turtle CLI
In my experience, using the current LTS version of Node.js (version 16.13.2) works best. Caveat: I could not complete the iOS instructions to...
Read more >
Using GitHub Actions to seamlessly deploy Expo ...
My first experience with mobile application development was using react native with Expo (in case you didn't know Expo is an open-source ...
Read more >
rn-native-hash - npm Package Health Analysis
MATCHING_BUILDS > 0 }} run: expo publish --release-channel=`rn-native-hash hash` # Build new Native Client if there are no - name: EAS Build ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found