Bug 40376 - IPA files are being created in a sub folder, not in the root build folder. This causes the build to fail
Summary: IPA files are being created in a sub folder, not in the root build folder. Th...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: unspecified
Hardware: PC Windows
: High major
Target Milestone: 4.1.0 (C7)
Assignee: Emanuel
URL:
Depends on:
Blocks:
 
Reported: 2016-04-14 02:20 UTC by Paul
Modified: 2016-06-24 16:05 UTC (History)
10 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:
VERIFIED FIXED

Description Paul 2016-04-14 02:20:19 UTC
# Steps to reproduce
Visual Studio 2015. Ensure build configuration has "Build ad-hoc/enterprise package(IPA)" selected
select iPhone as Platform
select Device
Build

# Expected behavior
Build success

# Actual behavior
Build fails with message The "CopyFileToWindows" task failed unexpectedly.
/bin/iPhone/Release/com.wahousing.test.app.ipa was not found on the Mac

ipa is created but within a sub folder of Release called "AssemblyName yyyy-MM-dd HH-mm-ss"
# Supplemental info (logs, images, videos)


# Test environment (full version information)
Comment 1 Jose Gallardo 2016-04-14 13:42:30 UTC
Hi Paul,

Can you please confirm what Xamarin version have you been using when hitting this issue? (My guess is that it was 4.1.x).

I'm moving this report to milestone C7 for visibility.

Thanks!
Comment 2 Paul 2016-04-15 00:37:44 UTC
Hi Jose,

Xamarin 4.1.0.313

Cheers,
Paul
Comment 3 Jose Gallardo 2016-04-15 03:58:41 UTC
Paul,

Thanks for the info.
We already have a fix for this issue, and it will be public on the next Preview refresh.

Thanks for the report!
Comment 5 Mohit Kheterpal 2016-05-02 12:53:31 UTC
I have checked this issue with C7 build of XVS i.e. XVS 4.1.0.462 and observed that this issue has been fixed i.e. now user is able to build and create ipa successfully.

http://screencast.com/t/iCP1tKLrBZ

Thanks
Comment 6 Night Owl 2016-05-26 06:20:04 UTC
Hey guys, I'me getting exactly the same "AssemblyName yyyy-MM-dd HH-mm-ss" issue, but on Xamarin Studio running on a Mac (version details below).

That also broke our jenkins script.

Can someone help me undertand which version has this fix?

Thanks
Night

=== Xamarin Studio Business ===

Version 6.0 (build 5166)
Installation UUID: 0a2578d7-b1f5-40ce-a518-cb5925d60c29
Runtime:
	Mono 4.4.0 (mono-4.4.0-branch/67b89ea) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000176

=== Xamarin.Profiler ===

Not Installed

=== Xamarin.Android ===

Version: 6.1.0.69 (Xamarin Business)
Android SDK: /Users/sibagy/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
		6.0   (API level 23)

SDK Tools Version: 25.1.6
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.3

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Not Installed

=== Xamarin Inspector ===

Version: 0.8.0.0
Hash: dc081aa
Branch: master
Build date: Tue Apr 26 23:07:44 UTC 2016

=== Apple Developer Tools ===

Xcode 7.3.1 (10188.1)
Build 7D1014

=== Xamarin.iOS ===

Version: 9.8.0.319 (Xamarin Business)
Hash: 7b89851
Branch: cycle7
Build date: 2016-05-20 16:56:02-0400

=== Xamarin.Mac ===

Not Installed

=== Build Information ===

Release ID: 600005166
Git revision: ec4f06cfaa9debdca2539e19edeafffe88ccd0cc
Build date: 2016-05-20 18:51:15-04
Xamarin addins: c7761d054f38e9a210822aba6356398af0c36fa9
Build lane: monodevelop-lion-cycle7

=== Operating System ===

Mac OS X 10.11.5
Darwin maui.local 15.5.0 Darwin Kernel Version 15.5.0
    Tue Apr 19 18:36:36 PDT 2016
    root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Xamarin Inspector 0.8.0.0
Comment 7 Night Owl 2016-05-26 06:20:56 UTC
Hey guys, I'me getting exactly the same "AssemblyName yyyy-MM-dd HH-mm-ss" issue, but on Xamarin Studio running on a Mac (version details below).

That also broke our jenkins script.

Can someone help me undertand which version has this fix?

Thanks
Night

=== Xamarin Studio Business ===

Version 6.0 (build 5166)
Installation UUID: 0a2578d7-b1f5-40ce-a518-cb5925d60c29
Runtime:
	Mono 4.4.0 (mono-4.4.0-branch/67b89ea) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000176

=== Xamarin.Profiler ===

Not Installed

=== Xamarin.Android ===

Version: 6.1.0.69 (Xamarin Business)
Android SDK: /Users/sibagy/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
		6.0   (API level 23)

SDK Tools Version: 25.1.6
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.3

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Not Installed

=== Xamarin Inspector ===

Version: 0.8.0.0
Hash: dc081aa
Branch: master
Build date: Tue Apr 26 23:07:44 UTC 2016

=== Apple Developer Tools ===

Xcode 7.3.1 (10188.1)
Build 7D1014

=== Xamarin.iOS ===

Version: 9.8.0.319 (Xamarin Business)
Hash: 7b89851
Branch: cycle7
Build date: 2016-05-20 16:56:02-0400

=== Xamarin.Mac ===

Not Installed

=== Build Information ===

Release ID: 600005166
Git revision: ec4f06cfaa9debdca2539e19edeafffe88ccd0cc
Build date: 2016-05-20 18:51:15-04
Xamarin addins: c7761d054f38e9a210822aba6356398af0c36fa9
Build lane: monodevelop-lion-cycle7

=== Operating System ===

Mac OS X 10.11.5
Darwin maui.local 15.5.0 Darwin Kernel Version 15.5.0
    Tue Apr 19 18:36:36 PDT 2016
    root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Xamarin Inspector 0.8.0.0
Comment 8 Marakai 2016-06-21 23:43:17 UTC
As of the current Stable release (at the time of writing this), this issue still exists and is breaking automated deployments via Atlassian Bamboo.

Is there an ETA for Stable, or at least a work-around, barring using a Preview release?
Comment 9 Anthony Lewandowski 2016-06-24 16:05:58 UTC
This issue is definitely not fixed. Please change the Status. Attempting a build with an IPA produces the "The "CopyFileToWindows" task failed unexpectedly." error. This issue shows up even with the latest from the Alpha channel. 

The IPA creation is process is absolutely necessary because Apple now requires applications build with sdk 9.0 or later to be packaged as proper IPA files.