-
Notifications
You must be signed in to change notification settings - Fork 528
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
Can remove MonoRuntimeProvider
from some process
?
#8387
Comments
You can probably user the That said if your process is written using .net then it won't work without the |
No the
Is auto gen. My AndroidManifest
final
can remove
from final |
I know it is auto generated. The |
Ok try remove it. |
It not work.
It can't match? |
Remove other thing is work, but remove |
Error msg is empty.
|
try
See if that works. |
no work |
I am trying to reproduce the issue. Can you provide an example of the C# code which has the |
You need to opt into the Manifest Merger. Its not on by default. Add the following to your
You can then user the following in
See https://learn.microsoft.com/en-us/xamarin/android/deploy-test/building-apps/build-properties#androidmanifestmerger for more details. |
Ok try it |
No, it still can't remove
|
I think the final manifest is in Those changes worked for me here. |
I found about three what is the final |
Context dotnet#8387 The value for `AndroidManifestMerger` should be updated to be `manifestmerger.jar`. This allows users to make use of the new features like `AndroidManifestOverlay` out of the box. The old system is still available, the users will need to add the following to their csproj. ``` <AndroidManifestMerger>legacy</AndroidManifestMerger> ```
Context dotnet#8387 The value for `AndroidManifestMerger` should be updated to be `manifestmerger.jar`. This allows users to make use of the new features like `AndroidManifestOverlay` out of the box. The old system is still available, the users will need to add the following to their csproj. ``` <AndroidManifestMerger>legacy</AndroidManifestMerger> ```
…8392) Context: #8387 Context: 2c6f5cd Context: f7ea4a3 Context: d794534 Update the value for `$(AndroidManifestMerger)` (f7ea4a3) to `manifestmerger.jar`. This allows users to make use of the new features like `@(AndroidManifestOverlay)` (d794534) out of the box. The old system is still available, users will need to add the following to their csproj: <AndroidManifestMerger>legacy</AndroidManifestMerger> AndroidX has been building with `$(AndroidManifestMerger)`=manifestmerger.jar for [over three years][0]. [0]: xamarin/AndroidX@c6c0e50
…8392) Context: #8387 Context: 2c6f5cd Context: f7ea4a3 Context: d794534 Update the value for `$(AndroidManifestMerger)` (f7ea4a3) to `manifestmerger.jar`. This allows users to make use of the new features like `@(AndroidManifestOverlay)` (d794534) out of the box. The old system is still available, users will need to add the following to their csproj: <AndroidManifestMerger>legacy</AndroidManifestMerger> AndroidX has been building with `$(AndroidManifestMerger)`=manifestmerger.jar for [over three years][0]. [0]: xamarin/AndroidX@c6c0e50
…8392) Context: #8387 Context: 2c6f5cd Context: f7ea4a3 Context: d794534 Update the value for `$(AndroidManifestMerger)` (f7ea4a3) to `manifestmerger.jar`. This allows users to make use of the new features like `@(AndroidManifestOverlay)` (d794534) out of the box. The old system is still available, users will need to add the following to their csproj: <AndroidManifestMerger>legacy</AndroidManifestMerger> AndroidX has been building with `$(AndroidManifestMerger)`=manifestmerger.jar for [over three years][0]. [0]: xamarin/AndroidX@c6c0e50
Android application type
.NET Android (net7.0-android, etc.)
Affected platform version
VS2022 net7
Description
I found a
MonoRuntimeProvider
in finalAndroidManifest.xml
I want to remove
MonoRuntimeProvider
from process:game
, cound write some config or command to remove it when building project?Steps to Reproduce
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: