-
Notifications
You must be signed in to change notification settings - Fork 74
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
Error at :app:processReleaseMainManifest when I try to build my app. #2322
Comments
Can you send me logs of your |
|
Did you add some new libs by any chance before getting this error? |
No, I have fixed the dependencies locally to match with Expo Doctor. I don't understand why I am still encountering this error. |
Can you try to do https://docs.expo.dev/debugging/runtime-issues/#android-studio? |
I have tried to build my app with Android Studio, but I keep encountering the same error with no additional information about it. I have this debug error, but I don't understand it. I have removed a problematic package, but nothing has changed.
|
I have executed this command
|
Okay The problem is on only android build ios is building successfully. |
With the command npx expo run:android
With the command npx expo run:ios
|
I have updated my Snack if you want. |
Alright, I found the issue: The problem stemmed from the fact that Expo hadn't added this code in the file
And when I tried using Expo's build function, for some reason, it wasn't picking up my changes in the file. So, I opted to directly use the command |
@szdziedzic Could this please be opened as a bug?
As far as we can tell this is a problem with the manifest placeholder not being added in build.gradle at build time. |
|
@Naveen-g09 Look at my comment #2322 (comment) and try the solution :) |
@H1B0B0 This won't work for managed expo apps because we don't have access to the Android folder. Hence why this needs to be reopened as a bug please. |
You can't try to build in local ? |
Not when it comes to managing an enterprise level application where we need to manage a CI pipeline for multiple devs to contribute to. Build is done on a build server using the eas-cli pipeline, and then distributed to stores. |
Yes. |
I don't have find any solutions for that. Sorry ): |
@EvanBacon any help you can get us from expo? |
This issue is also preventing me from building. This is a major problem for the managed workflow. Most people, as in my case, probably spent some time developing in the managed workflow and then when it's time to build, will be forced to eject to get around this issue. In my case, I did the following to test:
I tried removing packages that I thought could be problematic, and building after removing each one, I could not find the one causing the issue before running out of free builds, and I am not confident enough to upgrade to the paid plan, if this service will not work as documented. Any help on this would be much appreciated. Thanks.
|
@JayOfemi hiii, |
Best workaround I've found so far was given from a member of the expo discord. I used patch-project to create patch on the android build.gradle file which includes the required placeholder. steps:
This is however still just a workaround for a bug that needs to be investigated and fixed by Expo. |
@Naveen-g09 & @dpuckett Thanks for suggesting this workaround. It does look promising. @dpuckett I followed your instructions, but I get the below error when running
|
Build/Submit details page URL
No response
Summary
Hello, I have a build error that says: 'Manifest merger failed: Attribute data@scheme at AndroidManifest.xml requires a placeholder substitution but no value for is provided.' However, Expo doctor indicates no errors, and I can't seem to find where it might be coming from.
app.json
Managed or bare?
managed
Environment
Error output
No response
Reproducible demo or steps to reproduce from a blank project
https://snack.expo.dev/@hibobo/github.com-h1b0b0-trello-mobile-app
The text was updated successfully, but these errors were encountered: