Bug 24407 - Forms Template Sets assembly name to FormsTemplateiOS instead of the app name.
Summary: Forms Template Sets assembly name to FormsTemplateiOS instead of the app name.
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 1.2.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-11-10 14:28 UTC by Jon Goldberger [MSFT]
Modified: 2016-03-25 18:13 UTC (History)
4 users (show)

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


Attachments

Description Jon Goldberger [MSFT] 2014-11-10 14:28:19 UTC
## Description:

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.
Comment 2 Udham Singh 2014-11-11 07:08:57 UTC
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 :

Windows 8
VS 2013
Xamarin   3.7.248.0
Xamarin.iOS Build Host 8.4.0.16
Comment 3 Jason Smith [MSFT] 2016-03-25 18:13:34 UTC
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

Warm regards,
Xamarin Forms Team

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