Bug 18843 - [iOSforVS] Xamarin Store App deployment fails due to "..\Shared\Images\button-image.png"
Summary: [iOSforVS] Xamarin Store App deployment fails due to "..\Shared\Images\button...
Status: RESOLVED DUPLICATE of bug 17852
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Dominique Louis
URL:
Depends on:
Blocks:
 
Reported: 2014-04-07 16:28 UTC by Allie Miller
Modified: 2014-05-02 06:09 UTC (History)
8 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 17852

Description Allie Miller 2014-04-07 16:28:36 UTC
*Reported by user*

When attempting to deploy the Xamarin Store App from Visual Studio, the project fails to deploy to the iOS Simulator. Deploys successfully to iOS simulator from Mac Build Host.

*Steps to reproduce*:
1. Load the Xamarin Store App solution.

2. Change the Startup Project to the .IOS.

3. Set the Build options to use the iPhone Simulator.

4. Build the project.

5. Attempt to deploy the project to iOS simulator. 

*Results*:
Instead of a successfully deployment, ends with a Remote build step failed error message.

*The Fix*
The reported user found noticed that the button-image.png file was different from the other resources listed under the 
XamarinStore.iOS.csproj:

<BundleResource Include="..\Shared\Images\button-image.png">

After pointing to the button-image.png file in the Share\Images folder, the xml changed to:

<BundleResource Include="Resources\button-image.png"/>
And the project was deployable.
Comment 1 Sebastien Pouliot 2014-04-08 07:51:37 UTC
Please always include the version information of all the software being used.
Comment 2 Allie Miller 2014-04-08 12:31:35 UTC
Sorry! It's the current stable version of the software, which I can list below:

On Mac:
Xamarin Studio: 4.2.3.60
Runtime: 3.2.6
Xamarin.iOS: 7.2.0.2
Xamarin.Android: 4.12.2
Xcode: 5.0.2

On Windows:
VS2013
Xamarin.Android 4.12.2.1
Xamarin.iOS 1.10.47
Comment 3 Nate Cook 2014-04-09 16:08:35 UTC
I ran into this bug also (on the alpha channel). 

Microsoft Visual Studio Premium 2013
Version 12.0.30110.00 Update 1
Microsoft .NET Framework Version 4.5.51641
Xamarin.Android   4.12.02001 (a1e3982a)
Xamarin.iOS   1.10.47 (3d6a125d)

It seems that the iOS app doesn't handle resources that have been added as a link rather than copied to the resources folder. The frustrating part is that there was no indication of what the error was. Here were the symptoms I got:

In the Visual Studio output window:
1>Exception System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
1>Exception details can be found in the log file

In the log file at ~/Library/Logs/Xamarin/MonoTouchVS/mtbserver.log
[09-Apr-2014 11:26:09] Error: An error occurred (no details available)

I had no way of troubleshooting this error. Thankfully Allie Miller of Xamarin support pointed me to this bugzilla. The app is working for me now using the workaround (removing the linked resource and adding as non-linked).
Comment 4 Nate Cook 2014-04-24 19:17:02 UTC
This is a duplicate of bug 17852, which is in version 1.12 https://bugzilla.xamarin.com/show_bug.cgi?id=17852
Comment 5 Nate Cook 2014-04-24 19:17:40 UTC
I meant to say:

...which is *fixed* in version 1.12
Comment 6 Tajinder Singh 2014-05-02 06:09:33 UTC

*** This bug has been marked as a duplicate of bug 17852 ***