Closed kokorolx closed 3 years ago
Hi @kokorolx! I'm not exactly sure what's going on here. In the log you provided it says it's being "canceled", that's probably a manual action or a side-effect of another job failing.
I double-checked the behavior of this in bycedric/eas-monorepo-example
. Here you can see the "Publish to Expo" step succeeding and posting a QR code for the PR.
If you are able, could you provide a repository where this happens? With that, I can do some tests to see what part is blocking the action.
Hi @kokorolx! I'm not exactly sure what's going on here. In the log you provided it says it's being "canceled", that's probably a manual action or a side-effect of another job failing.
I double-checked the behavior of this in
bycedric/eas-monorepo-example
. Here you can see the "Publish to Expo" step succeeding and posting a QR code for the PR.If you are able, could you provide a repository where this happens? With that, I can do some tests to see what part is blocking the action.
Oh, I canceled
because it was running up to 2 hours. It published to repo successfully but it does not stop to progress publish
.
I will copy your workflows/preview.yml
and run it again.
@byCedric
After updated the github/workflows/preview.yml
It's still not working.
And it's still running.
My new preview.yml
name: preview
on: [workflow_dispatch, pull_request]
jobs:
preview:
name: Publish preview
runs-on: ubuntu-latest
if: github.event.pull_request.head.repo.full_name == 'kokorolx/share_opus_mobile_app'
strategy:
matrix:
app: [managed]
steps:
- name: Setup repo
uses: actions/checkout@v2
- name: Setup Node
uses: actions/setup-node@v1
with:
node-version: 14.x
- name: Setup Expo
uses: expo/expo-github-action@v5
with:
expo-cache: true
expo-version: 4.x
expo-username: ${{ secrets.EXPO_CLI_USERNAME }}
expo-password: ${{ secrets.EXPO_CLI_PASSWORD }}
- name: Find cache
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- name: Restore cache
uses: actions/cache@v2
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
- name: Install dependencies
run: yarn install --frozen-lockfile --check-files
- name: Build packages
run: yarn build
- name: Publish to Expo
run: expo publish --release-channel=pr-${{ github.event.number }}
- name: Get deployment link
run: echo "::set-output name=path::@kokoro.lee/use-expo?release-channel=pr-${{ github.event.number }}"
id: expo
- name: Comment deployment link
uses: unsplash/comment-on-pr@master
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
msg: You can preview [`apps/${{ matrix.app }}` here](https://expo.io/${{ steps.expo.outputs.path }}).<br><br><a href="https://exp.host/${{ steps.expo.outputs.path }}"><img src="https://api.qrserver.com/v1/create-qr-code/?size=400x400&data=exp://exp.host/${{ steps.expo.outputs.path }}" height="200px" width="200px"></a>
If you are able, could you provide a repository where this happens? With that, I can do some tests to see what part is blocking the action.
Oh sorry, but if you want any info, I will provide it for you.
Do I need to upgrade my expo account to Priority
plan?
Hmm, your workflow seems good. I don't know why it's blocking the publish step for you. expo publish
isn't affected by the priority plan, only your builds are queued without it. I'm afraid I need access to a repository to fully investigate this.
Oh, I found that issue by the package: @ui-kitten/metro-config
I removed it and now the github action working correctly.
Thank you for your support @byCedric
Awesome! Glad you got it working :)
Description of the bug
How would you shortly summarise the issue?
I want every PR will create a release channel, and I choose GitHub action to do that. My environment:
My package.json
My app.json
My workflow.yml
To Reproduce
What steps did you perform which led to this issue?
I create the PR on GitHub, and the Action will auto-run. After
Publish complete
it not continue.Expected behavior
What did you expect to have happened? After
Publish complete
it not continue.Actual behavior
What did it actually result in? It took me 2 hours to take this action, when I found out it couldn't continue, I canceled this action.
Here is the full log of this action: Full log
Additional context
Can you further explain the issue? E.g., information about version/environment or screenshots.
My question is: How can I continue if
Publish complete
?Sorry for my poor English.