Bug 56754 - warning MT0095: Aot files could not be copied to the destination directory (with extensions)
Summary: warning MT0095: Aot files could not be copied to the destination directory (w...
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools (show other bugs)
Version: master
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Manuel de la Peña
Depends on:
Reported: 2017-05-23 10:34 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2017-09-27 19:40 UTC (History)
8 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:

build.log (807.98 KB, text/plain)
2017-05-23 10:34 UTC, Rolf Bjarne Kvinge [MSFT]
msymtest.zip (test project) (14.13 KB, application/zip)
2017-05-23 10:34 UTC, Rolf Bjarne Kvinge [MSFT]

Description Rolf Bjarne Kvinge [MSFT] 2017-05-23 10:34:17 UTC
Created attachment 22384 [details]


* Create new project from a template.
* Add an extension.
* Build for Release|Device

The build log contains two warnings:

MTOUCH : warning MT0095: Aot files could not be copied to the destination directory /Users/rolf/Projects/msymtest/myactionextension/bin/iPhone/Release/myactionextension.appex.mSYM
MTOUCH : warning MT0095: Aot files could not be copied to the destination directory /Users/rolf/Projects/msymtest/myactionextension/bin/iPhone/Release/myactionextension.appex.mSYM
Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-05-23 10:34:52 UTC
Created attachment 22385 [details]
msymtest.zip (test project)
Comment 2 Edward Brey 2017-06-02 16:31:03 UTC
These warnings appear when the build is launched via Visual Studio for Windows as well. Can we get a quick answer as to whether these warnings are benign?
Comment 3 Manuel de la Peña 2017-06-06 16:06:51 UTC
@Rolf can you provide a reply?
Comment 4 Rolf Bjarne Kvinge [MSFT] 2017-06-07 14:00:08 UTC
@Edward, these warnings won't break your app (but may prevent symbolication of crash reports from working properly).
Comment 5 subbota-job 2017-07-12 08:33:19 UTC
Impossibility getting symbolication of crash report is very big problem! It breaks support and prevents us fixing bugs!
Comment 6 Sebastien Pouliot 2017-07-17 21:00:57 UTC
To clarify those are the mono .mSYM files, not the .dSYM files used by Apple tools.

If you're not using `mono-symbolicate` [1] in your workflow then this won't affect you. This would also be an issue on the extension(s) mentioned by the warnings (not on the main executable).

[1] http://www.mono-project.com/docs/about-mono/releases/4.6.0/#mono-symbolicate
Comment 7 Manuel de la Peña 2017-09-11 15:34:33 UTC
I have investigated the issue. It looks like we are not getting the aot files from the compiler and mtouch is not able to copy them over since they are not created. I have updated mtouch to notify about this issue. 

Will continue working on this to understand what is going on with mono not files on extensions.
Comment 8 Sebastien Pouliot 2017-09-25 21:12:59 UTC
*** Bug 59712 has been marked as a duplicate of this bug. ***
Comment 9 ebugden 2017-09-27 19:27:25 UTC
**** Critical Issue *****

The result of running the compilation to create the IPA file is that the IPA file is not copied to the build server (MAC Computer)

I can not use the Show IPA on Build Server.

I can not use the Application Loader from Apple to load the IPA file to the Apple Store.

This is causing me to be unable to process my application to the place it into the Apple Store.

I need a work around for this issue.
Comment 10 Sebastien Pouliot 2017-09-27 19:40:37 UTC
@ebugden this is not related to this bug (or that warning). Please file a bug report for that specific issues, include the full build logs and version information, and someone will have a look at it.

Note You need to log in before you can comment on or make changes to this bug.