eas device:create - Missing `iosUrlScheme` in provided options: {}

[deelo55]

Build/Submit details page URL

https://expo.dev/accounts/heliosx/projects/levity

Summary

When running eas device:create I get the following error:

google-sign-in without Firebase config plugin: Missing `iosUrlScheme` in provided options: {}
    Error: device:create command failed.

I am configuring the iosUrlScheme using eas.json and .env files:

        '@react-native-google-signin/google-signin',
        {
          iosUrlScheme: process.env.REVERSED_GOOGLE_CLIENT_ID,
        },

.env

#GOOGLE SIGN IN
REVERSED_GOOGLE_CLIENT_ID = com.googleusercontent.apps.EXAMPLE

eas.json

    "preview": {
      "distribution": "internal",
      "env": {
        "REVERSED_GOOGLE_CLIENT_ID": "com.googleusercontent.apps.EXAMPLE

Managed or bare?

Bare

Environment

expo-env-info 1.2.0 environment info:
System:
OS: macOS 15.0
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.8.3 - ~/.nvm/versions/node/v20.17.0/bin/npm
Managers:
CocoaPods: 1.15.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.0, iOS 18.0, macOS 15.0, tvOS 18.0, visionOS 2.0, watchOS 11.0
IDEs:
Android Studio: 2024.1 AI-241.18034.62.2411.12071903
Xcode: 16.0/16A242d - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.37 => 51.0.37
expo-router: ~3.5.23 => 3.5.23
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.5 => 0.74.5
react-native-web: ^0.19.12 => 0.19.12
npmGlobalPackages:
eas-cli: 12.4.1
Expo Workflow: bare

Error output

google-sign-in without Firebase config plugin: Missing `iosUrlScheme` in provided options: {}
    Error: device:create command failed.

Reproducible demo or steps to reproduce from a blank project

Setup google authentication as described here:
https://docs.expo.dev/guides/google-authentication/
and make your app.config.js to load like:

        '@react-native-google-signin/google-signin',
        {
          iosUrlScheme: process.env.REVERSED_GOOGLE_CLIENT_ID,
        },

Run eas device:create

[szdziedzic]

As of today, EAS CLI does not support .env files at all. Only Expo CLI does (npx expo ...). The eas device:create command also doesn't work with build profiles 🤔 So probably to make it work you would need to do REVERSED_GOOGLE_CLIENT_ID=value eas device:create. We should probably let people use env vars in some way with it though 🤔.

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[deelo55]

As of today, EAS CLI does not support .env files at all. Only Expo CLI does (npx expo ...). The eas device:create command also doesn't work with build profiles 🤔 So probably to make it work you would need to do REVERSED_GOOGLE_CLIENT_ID=value eas device:create. We should probably let people use env vars in some way with it though 🤔.

I don't have an issue with other EAS CLI commands as they reference the profile and use EAS.json. The device:create command doesn't look in eas.json or .env.

Alternatively, does create:device really need to do any validation?

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.