Closed erickreutz closed 11 months ago
Hi @erickreutz, thanks for reporting this issue! I've just patched support for multiple app schemes, this was added lately and wasn't updated in this action yet. See PR #244 for this.
The other issue, related to the QR code prefixing schemes with exp+
, work is on it's way. But, since this is part of our internal services, it's on a private repo.
Will provide an update once I have more!
The multi-scheme fix, and an optional "overwrite" app-scheme
input property are released on expo/expo-github-action/preview@v8
.
The QR code with exp+
prefix will likely take a bit longer because of a US holiday.
Fix has been merged and released as expo/expo-github-action/preview@8
. Website fix is a minor textual change, which we don't need to wait for.
@byCedric thank you!
Firstly
app.json
defines the type ofscheme
asstring | string[]
and from what I can tell this action doesn't account for an array. https://github.com/expo/expo-github-action/blob/57dcabe749340c8c995ee0334cd7c547c35770d0/src/actions/preview.ts#L113I've also noticed that QR codes break when using custom schemes that deviate from the default project
slug
. For example if the scheme in myapp.json
ismyapp-dev
and the slug ismyapp
and thebundleId
iscom.org.myapp
thenexpo prebuild
will add the following schemes toInfo.plist
:You'll then use the custom scheme to get a QR code here
This returns a QR code that the expo-dev-client will not understand because it appends
exp+
to all app schemes andexp+myapp-dev
is not a known scheme.You can see an example of this problem at https://expo.dev
It says "use appScheme" from app.json but it's not the
appScheme
it's expecting - it's the project slug because the appScheme (if it's user-defined) won't work with theexp+
prefix.