-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QR codes broken when using custom schemes #240
Comments
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 Will provide an update once I have more! |
The multi-scheme fix, and an optional "overwrite" The QR code with |
Fix has been merged and released as |
@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.expo-github-action/src/actions/preview.ts
Line 113 in 57dcabe
I'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.The text was updated successfully, but these errors were encountered: