Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When starting a new Forms PCL project in Visual Studio, the Assembly name is set to FormsTemplateiOS instead of the app name. This results in a warning that the assembly name and the app name do not match an thus may not be symbolicated properly.
This is the warning:
Warning 1 The executable name (FormsTemplateiOS) and the app name (BuildErrorsiOS.app) are different, this may prevent crash logs from getting symbolicated properly. C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets 385 3 BuildErrors.iOS
## Steps to reproduce
1. Open Visual Studio and create a new Forms PCL project.
2. Build and launch to device or simulator
Expected result: no warning about assembly name being different form the app name
Actual result: Above warning generated about assembly name being different form the app name
## To resolve:
Change the assembly name to match the app name.
I have checked this issue with the help of instructions provided in bug description and observed the same behaviour mentioned in bug description. Please refer the screencast : http://www.screencast.com/t/NaGM7bfwu
Environment Info :
Xamarin.iOS Build Host 184.108.40.206
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team