Error Failed to build the app: No package name found

[edwardlarsson94]

Minimal reproducible example

The error occurs when I run the command "eas build --platform ios" for a react native project using expo, it does not let me compile and does not go beyond the install pod.

Summary

Cuando ejecute el comando "eas build --platform ios" este me debe generar el compilado para ios para subirlo a la app store pero hace horas ese mismo codigo me funcionaba y ahora ya no me deja compilar me genera el siguiente error:

Using Expo modules
[Expo] Enabling modular headers for pod ExpoModulesCore
[Expo] Enabling modular headers for pod ReactCommon
[Expo] Enabling modular headers for pod EXImageLoader
Auto-generating .xcode.env.local with $NODE_BINARY=/Users/expo/.nvm/versions/node/v16.18.1/bin/node
[stderr]
error Failed to build the app: No package name found. Found errors in /Users/expo/workingdir/build/node_modules/expo-intent-launcher/android/src/main/AndroidManifest.xml.
[!] Invalid Podfile file: unexpected token at 'info Run CLI with --verbose flag for more details.
'.

from /Users/expo/workingdir/build/ios/Podfile:15

-------------------------------------------

use_expo_modules!

config = use_native_modules!

-------------------------------------------

Error: Unknown error. See logs for more information.

Environment

expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.1
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.17 - ~/node_modules/.bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v16.16.0/bin/npm
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8512546
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
npmPackages:
expo: ~47.0.12 => 47.0.14
react: 18.1.0 => 18.1.0
react-dom: 18.1.0 => 18.1.0
react-native: 0.70.8 => 0.70.8
react-native-web: ~0.18.7 => 0.18.12
react-navigation: ^4.4.4 => 4.4.4
npmGlobalPackages:
eas-cli: 3.15.0
expo-cli: 6.0.8
Expo Workflow: bare

[expo-bot]

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

• "How to create a Minimal, Reproducible Example"
• "How to narrow down the source of an error"

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.

[VictorioMolina]

@brentvatne @edwardlarsson94 Same here, in my case I get this output:

Using Expo modules

[Expo] Enabling modular headers for pod ExpoModulesCore

[Expo] Enabling modular headers for pod ReactCommon

[Expo] Enabling modular headers for pod SDWebImage

[Expo] Enabling modular headers for pod SDWebImageWebPCoder

[Expo] Enabling modular headers for pod SDWebImageAVIFCoder

[Expo] Enabling modular headers for pod SDWebImageSVGCoder

[Expo] Enabling modular headers for pod EXImageLoader

Auto-generating `.xcode.env.local` with $NODE_BINARY=/Users/expo/.nvm/versions/node/v16.18.1/bin/node

[stderr] 
error Failed to build the app: No package name found. Found errors in /Users/expo/workingdir/build/node_modules/expo-image/android/src/main/AndroidManifest.xml.

[!] Invalid `Podfile` file: unexpected token at 'info Run CLI with --verbose flag for more details.

'.

 #  from /Users/expo/workingdir/build/packages/app/ios/Podfile:17

 #  -------------------------------------------

 #  # @generated end react-native-maps

 >    config = use_native_modules!

 #  

 #  -------------------------------------------

Error: Unknown error. See logs for more information.

Maybe something has changed on EAS? I am just literally trying to build a project I compiled last week (6 days ago), without major changes, and now getting this problem.

Currently, I am using Expo SDK 47 and the non-modular Firebase JS SDK, but upgrading to Expo 48 (something that I have tried but cannot do right now in my real scenario) fixes the issue.

These are my resolutions:

  "resolutions": {
    "expo-modules-autolinking": "~1.0.0",
    "@expo/config-plugins": "^5.0.2",
    "@expo/prebuild-config": "^5.0.5"
  }

EAS Version: 3.15.0

[JacobDel]

+1, please reopen this issue

[tiagopazhs]

• 1