Skip to content

_XARemapMembersFilePath is not being treated as a path in the obj folder #8095

Description

@Archit-Pikle

Android application type

.NET Android (net7.0-android, etc.)

Affected platform version

VS 17.6.0 Preview 7.0

Description

The xa-internal/xa-remam-members.xml created for each build is not being treated as a path in the obj folder but is rather being configured as a relative path.
This is causing the file to be added in git changelog.

The workaround we are using is to explicitly add the file in our .gitignore file.

We think this is happening because MonoAndroidAssetsDirIntermediate is defined after defining _XARemapMembersFilePath in https://github.com/xamarin/xamarin-android/blob/main/src/Xamarin.Android.Build.Tasks/Xamarin.Android.Common.targets

Steps to Reproduce

  1. Create a .NET App for a github project.
  2. Make some changes, build and deploy the app.

Expected: xa-internal/xa-reamp-members.xml should not be included in the git changelog.
Actual: xa-internal/xa-remap-members.xml is included in the git changelog.

Did you find any workaround?

The workaround is to explicitly add xa-internal/xa-remap-members.xml in the .gitignore file

Relevant log output

No response

Activity

  1. changed the title [-]`xa-internal/xa-remap-members.xml` is not being excluded in git changelog[/-] [+]_XARemapMembersFilePath is not being treated as a path in the obj folder[/+] on Jun 1, 2023
  2. jonathanpeppers commented on Jun 2, 2023

    @jonathanpeppers
    Member
  3. added
    need-infoIssues that need more information from the author.
    and removed
    needs-triageIssues that need to be assigned.
    on Jun 2, 2023
  4. Archit-Pikle commented on Jun 2, 2023

    @Archit-Pikle
    Author

    Yes this too goes away if we remove the https://www.nuget.org/packages/Microsoft.Intune.Maui.Essentials.android/9.5.2-beta2 dependency from the project

  5. ghost removed
    need-infoIssues that need more information from the author.
    on Jun 2, 2023
  6. ghost added
    need-attentionA xamarin-android contributor needs to review
    on Jun 2, 2023
  7. Archit-Pikle commented on Nov 20, 2023

    @Archit-Pikle
    Author

    I'm still able to repro this issue on a .NET 7 app. However, this is resolved on a .NET 8 app.
    Is this by design?

  8. jonpryor commented on Nov 20, 2023

    @jonpryor
    Contributor

    @Archit-Pikle asked:

    Is this by design?

    Largely, yes. Even when using .NET 8, the .NET 7 support is almost entirely separate from the .NET 8 build system. (Implementation-wise, the .NET 8 workload references the .NET 7 workload packages.). Thus, in order for any .NET 7 build to get build-system fixes, those fixes need to be applied to the release/7.0.4xx branch, a new .NET 7 build released, and the .NET 8 workload updated to reference the new .NET 7 bits.

    Changes present in the .NET 8 workload do not apply to .NET 7 builds, even when multitargeting from a .NET 8 installation.

  9. locked and limited conversation to collaborators on Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area: App+Library BuildIssues when building Library projects or Application projects.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions