Skip to content

Copy .msym files to output path on publish #8001

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

Open
Redth opened this issue Apr 29, 2023 · 2 comments
Open

Copy .msym files to output path on publish #8001

Redth opened this issue Apr 29, 2023 · 2 comments
Assignees
Labels
Area: App+Library Build Issues when building Library projects or Application projects.

Comments

@Redth
Copy link
Member

Redth commented Apr 29, 2023

Android application type

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

Affected platform version

N/A

Description

dotnet public -f net7.0-android -o ./artifacts causes the .apk and .aab to output correctly, however it would be good to also get the .msym files copied here (or if that seems weird by default, perhaps another property to specify the path to copy them to).

Related: dotnet/macios#18190

Steps to Reproduce

^

Did you find any workaround?

No response

Relevant log output

No response

@Redth Redth added Area: App+Library Build Issues when building Library projects or Application projects. needs-triage Issues that need to be assigned. labels Apr 29, 2023
@Redth
Copy link
Member Author

Redth commented Apr 29, 2023

Looks like MonoSymbolArchive=True needs to be set to actually produce them, and then they might output there? Perhaps we should consider defaulting that to true for publish with release configs?

However setting it to true yields:

/usr/local/share/dotnet/packs/Microsoft.Android.Sdk.Darwin/33.0.46/tools/Xamarin.Android.Common.targets(2202,3): error MSB6004: The specified task executable location "/usr/local/share/dotnet/packs/Microsoft.Android.Sdk.Darwin/33.0.46/tools/Darwin/mono-symbolicate" is invalid. 

@steveisok @jonathanpeppers do we not have mono-symbolicate in our workloads?

@jpobst jpobst removed the needs-triage Issues that need to be assigned. label Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: App+Library Build Issues when building Library projects or Application projects.
Projects
None yet
Development

No branches or pull requests

4 participants