EAS Update: Preview with comment

Description of the feature

expo/expo-github-action/preview-comment to be compatible with EAS Update.

Motivation

We have examples for EAS build in the README and it is possible to open channels/branches with the expo app but with classic release channels we are able to scan a QR code.

Additional context

      - name: Setup Expo
        uses: expo/expo-github-action@7.2.0
        with:
          expo-version: latest
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}

      - name: Publish preview
        run: eas update --branch pr-${{ github.event.number }} --message 'Update with commit ${{ github.sha }}'

      - name: Comment preview
        uses: expo/expo-github-action/preview-comment@7.2.0
        with:
          channel: pr-${{ github.event.number }}

Comment preview will use classic release channels to generate the QR code, so when scanning the code, it won’t work.

[robertoyoc]

Got it working by doing:

      - name: Publish preview
         run: eas update --branch pr-${{ github.event.number }} --message 'Update with commit ${{ github.sha }}'
      - name: Comment preview
         uses: expo/expo-github-action/preview-comment@7.2.0
         with:
          message: '<h2>Your Project!</h2><h3>Channel: pr-${{ github.event.number }}</h3><a href="exp+<YOUR_SCHEME>://expo-development-client/?url=<YOUR_EXPO_UPDATES_URL>%3Fchannel-name%3Dpr-${{ github.event.number }}"><img src="https://qr.expo.dev/development-client?appScheme=exp%2B<YOUR_SCHEME>&url=<YOUR_EXPO_UPDATES_URL>%3Fchannel-name%3Dpr-${{ github.event.number }}" height="200px" width="200px"></a>'

Replace:

• < YOUR_SCHEME >
• < YOUR_EXPO_UPDATES_URL > with your urlEncoded expo updates url.

Also, you need an internal distribution (development) build to be able to scan the QR.

[lachenmayer]

We ran into this issue ourselves, we’re using the following fork: https://github.com/expo/expo-github-action/compare/main...lachenmayer:expo-github-action:eas-updates-qr

You can use this with uses: lachenmayer/expo-github-action/preview-comment@eas-updates-qr to try it out, but please don’t rely on it…

This checks whether project.updates.url exists, and creates a QR code compatible with a dev client instead of the Expo Go QR code if so.

Happy to open a PR if you agree with the approach.