Bug 17624 - MonoTouchBuildNative_UploadChanges -- FAILED
Summary: MonoTouchBuildNative_UploadChanges -- FAILED
Status: RESOLVED INVALID
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Windows
: Normal normal
Target Milestone: 3.7
Assignee: vsx
URL:
Depends on:
Blocks:
 
Reported: 2014-02-05 15:39 UTC by Andy
Modified: 2014-07-31 06:43 UTC (History)
5 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 INVALID

Description Andy 2014-02-05 15:39:39 UTC
Saying hello to the remote server at http://10.0.0.10:49192/
Done executing task "MonoTouchBuildNative_SayHello".
Task "Message"
Fetching manifest...
Done executing task "Message".
Task "MonoTouchBuildNative_FetchManifest"
Updating information about the remote server
Done executing task "MonoTouchBuildNative_FetchManifest".
Task "Message"
Uploading changes...
Done executing task "Message".
Task "MonoTouchBuildNative_UploadChanges"
Synchronizing with the remote server
Remote build step failed.
The specified server cannot perform the requested operation.

Done executing task "MonoTouchBuildNative_UploadChanges" -- FAILED.
Done building target "_BuildNativeApplication" in project "LogicGames.csproj" -- FAILED.
Done building project "LogicGames.csproj" -- FAILED.
Build FAILED.
Error: Cancelled
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Comment 1 Prashant manu 2014-02-06 00:48:47 UTC
Could you please provide us the screenshot/test steps for this?
Comment 2 Andy 2014-02-06 01:11:35 UTC
I simply clean / build / deploy

No time to provide yet one more test project
Comment 3 Marek Habersack 2014-02-06 03:33:23 UTC
It's not possible to proceed here without more information. The error included in the original report does not give us anything. Please reopen only when/if you are able to provide more information from the following list, thanks:

  - screencast/screenshot
  - contents of all the logs during the failure (build server, application log 
    from the mac machine, *verbose* build log from VS)
  - *versions* of the software involved
Comment 4 Andy 2014-02-06 09:40:46 UTC
- screenshot: of what ? Of VS ? There's nothing to see. Just click Clean,Rebuild and Deploy on the project.

- I have a couple of logs handy: it's bug n.67 I reported, it's time consuming get 3-4 logs from different parts every time or to provide you a repro test project. I suggest - given on how many bugs I find - you add an easier way to package and pass you the logs. You know, so we don't have to lose half an hour every time we're stuck with a new bug.

- VS 2010 ultimate. 7.0.5 on mac, 1.10.39 VS
Comment 7 Marek Habersack 2014-02-06 10:51:30 UTC
(In reply to comment #4)
> - screenshot: of what ? Of VS ? There's nothing to see. Just click
> Clean,Rebuild and Deploy on the project.
*screencast* - a recording of all your actions as you perform them.
 
> - I have a couple of logs handy: it's bug n.67 I reported, it's time consuming
> get 3-4 logs from different parts every time or to provide you a repro test
> project. I suggest - given on how many bugs I find - you add an easier way to
> package and pass you the logs. You know, so we don't have to lose half an hour
> every time we're stuck with a new bug.
> 
> - VS 2010 ultimate. 7.0.5 on mac, 1.10.39 VS