Skip to content
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

EAS Fastlane failing #1674

Closed
Wolfleader101 opened this issue Feb 6, 2023 · 4 comments
Closed

EAS Fastlane failing #1674

Wolfleader101 opened this issue Feb 6, 2023 · 4 comments
Labels
incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues needs review Issue is ready to be reviewed by a maintainer

Comments

@Wolfleader101
Copy link

Build/Submit details page URL

https://expo.dev/accounts/wolfleader101/projects/pot-pirate/builds/22ee2a4d-2a2c-426d-bfde-57cd742e04e1

Summary

It is failing in Run Fastlane at the end with the following error. This error only started occurring as of yesterday night.

› Executing react-native Pods/FBReactNativeSpec » [CP-User] Generate Specs
    Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'PotPirate' from project 'PotPirate')
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'PotPirate' from project 'PotPirate')
    Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')
▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸     PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/expo/Library/Developer/Xcode/DerivedData/PotPirate-byuqhcbphskqumejjvyrwsnwvpze/Build/Intermediates.noindex/ArchiveIntermediates/PotPirate/IntermediateBuildFilesPath/Pods.build/Debug-iphoneos/FBReactNativeSpec.build/Script-46EB2E00015E30.sh (in target 'FBReactNativeSpec' from project 'Pods')
▸ (1 failure)
** ARCHIVE FAILED **
The following build commands failed:
    PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/expo/Library/Developer/Xcode/DerivedData/PotPirate-byuqhcbphskqumejjvyrwsnwvpze/Build/Intermediates.noindex/ArchiveIntermediates/PotPirate/IntermediateBuildFilesPath/Pods.build/Debug-iphoneos/FBReactNativeSpec.build/Script-46EB2E00015E30.sh (in target 'FBReactNativeSpec' from project 'Pods')
(1 failure)
Exit status: 65

Managed or bare?

Managed

Environment

expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 16.3.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
npm: 7.15.1 - C:\Program Files\nodejs\npm.CMD
SDKs:
Android SDK:
API Levels: 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0
System Images: android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: Version 2020.3.0.0 AI-203.7717.56.2031.7678000
Expo Workflow: managed

Expo Doctor:
🎉 Didn't find any issues with the project!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

List of my depedencies

  "dependencies": {
    "@acme/api": "^0.1.0",
    "@acme/tailwind-config": "^0.1.0",
    "@config-plugins/react-native-ble-plx": "^5.0.0",
    "@expo/vector-icons": "^13.0.0",
    "@react-native-community/masked-view": "^0.1.11",
    "@react-navigation/bottom-tabs": "^6.5.4",
    "@react-navigation/native": "^6.1.3",
    "@react-navigation/native-stack": "^6.9.9",
    "@shopify/flash-list": "1.3.1",
    "@tanstack/react-query": "^4.24.4",
    "@trpc/client": "^10.10.0",
    "@trpc/react-query": "^10.10.0",
    "@trpc/server": "^10.10.0",
    "clsx": "^1.2.1",
    "expo": "~47.0.13",
    "expo-dev-client": "~2.0.1",
    "expo-location": "~15.0.1",
    "expo-splash-screen": "~0.17.5",
    "expo-status-bar": "~1.4.2",
    "nativewind": "^2.0.11",
    "react": "18.1.0",
    "react-dom": "18.1.0",
    "react-native": "0.70.5",
    "react-native-auth0": "^2.17.0",
    "react-native-ble-plx": "^2.0.3",
    "react-native-gesture-handler": "~2.8.0",
    "react-native-maps": "1.3.2",
    "react-native-modal": "^13.0.1",
    "react-native-reanimated": "~2.12.0",
    "react-native-safe-area-context": "4.4.1",
    "react-native-screens": "~3.18.2"
  },```
@Wolfleader101 Wolfleader101 added the needs review Issue is ready to be reviewed by a maintainer label Feb 6, 2023
@Wolfleader101
Copy link
Author

Wolfleader101 commented Feb 6, 2023

Update:

Updating to react native 0.71.2 fixed the bug, however expo doctor will now complain about the react native version. (Still unsure the true cause of this bug)

@brentvatne brentvatne added the incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues label Feb 6, 2023
@expo-bot
Copy link
Contributor

expo-bot commented Feb 6, 2023

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

@expo-bot expo-bot closed this as completed Feb 6, 2023
@brentvatne
Copy link
Member

unable to reproduce this. I looked at your xcode logs from the build you linked to and saw this:

/Users/expo/workingdir/build/apps/expo/ios/Pods/../../../../node_modules/react-native/React/FBReactNativeSpec/../../scripts/react_native_pods_utils/script_phases.sh: line 24: syntax error near unexpected token `{
'

my first guess is this may be related to react-native support for pnpm workspaces. i believe this was fixed by our very own @byCedric in 0.71: facebook/react-native#35430

you can try using patch-package to apply the same fix. we're working on getting react-native 0.71 support in sdk 48 for a release this quarter.

@Wolfleader101
Copy link
Author

Thanks,
Will look into using patch package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

3 participants