none
Can't deploy to build 14356

    Question

  • Any attempt to deploy an app from Visual Studio to build 14356.1000 on Lumia 930s or 950s results in an error: -2147014836.

    This is the case for an existing app that was deployed immediately before the upgrade to new version with no problem, or with any new test app.

    At least three developers reporting this (so that's all of us). Reporting via Insider forums gets sent here.

    A.

    Friday, June 03, 2016 3:24 PM

Answers

All replies

  • May I please know the version of visual studio you are using (i.e. RTM or Update 2 of Visual Studio 2015)?

    Your explanation does not seem to be clear.

    Friday, June 03, 2016 3:42 PM
  • Same here!

    I tried on two different development systems. This is really an issue of that build!

    RoP

    Friday, June 03, 2016 8:43 PM
  • "Visual Studio 2015 Enterprise Update 2" with all current updates.

    Deploy to other devices with older builds is working!

    RoP

    Friday, June 03, 2016 8:45 PM
  • I'm using VS Community 2015, 14/0/25123.00 Update 2

    A.

    Friday, June 03, 2016 9:35 PM
  • Same problem here on my 950. Using VS2015 Update 2
    Saturday, June 04, 2016 8:45 AM
  • I have the same won't deploy problem for my 640 on build 14356.1000.  Have VS2015 Comm Update 2 May-revision.

    Won't sideload either, but useable thru file explorer.

    My 635 with WP8.1 is deployable so it's not any issue with VS or OS/hardware.

    I reset the 640 and restored with a backup, and it didn't help.  I was about to reset without a backup, but I now think it won't make any difference.

    Saturday, June 04, 2016 9:27 AM
  • The same here on an up-to-date VS2015 Enterprise and Lumia 730.
    Monday, June 06, 2016 7:18 AM
  • Same issue, using VS2015 Enterprise (14.0.25123.00 Update 2), WP10 build 14356 on Lumia 830.

    Deploy succeeds on other phones (Lumia 820 w/build 10586).

    May this be an issue within VS's target platform lookup (which may explain why it works on my 820)?

    from csproj:

    <TargetPlatformVersion>10.0.10586.0</TargetPlatformVersion>
    <TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion>

    Tried to hack TargetPlatformVersion to my build version, but of course didn't work because VS was looking for the related SDK...

    Thanks


    PS: moreover, with this build the recovery tool fails to revert to WP8.1 (so to move back to "slow" builds and get to work again)




    • Edited by giannit Monday, June 06, 2016 7:24 PM
    Monday, June 06, 2016 7:05 PM
  • Hi amacadabra,

    Since different community members got the same issue as yours, if possible, you can submit this feedback to Microsoft Connect feedback portal: http://connect.microsoft.com/VisualStudio/feedback/CreateFeedback.aspx,Microsoft engineers will evaluate them seriously. Thanks for your understanding.

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, June 07, 2016 12:13 PM
    Moderator
  • ...already done!
    Tuesday, June 07, 2016 12:28 PM
  • @RoDiPa,

    Would you mind sharing us the connect report link here? So other members could help you vote and add comments in your report.

    Sincerely,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, June 08, 2016 11:21 AM
    Moderator
  • Of course!

    Here is the Microsoft Connect link for that issue:
    https://connect.microsoft.com/VisualStudio/feedback/details/2794469/cannot-deploy-to-build-14356

    Regards,
    RoDiPa

    Wednesday, June 08, 2016 11:34 AM
  • Unfortunately the error is not fixed in the next Insider Build 10.0.14361.0! I got the same error after the update!

    Is this never tested from the Microsoft side?
    How can we build apps, when the deploying is not working. Sorry...!

    Wednesday, June 08, 2016 9:05 PM
  • Hi RoDiPa,

    Thanks for your response. As you already submit one feedback on the Microsoft Connect site, let's focus on the case on that channel, may the senior members can provide more professional support.

    Like the comments in this report:

    https://connect.microsoft.com/VisualStudio/feedback/details/2794469/cannot-deploy-to-build-14356

    You could collect the log and upload it to the above report using the Collection Tool, the report team will help you analyze the log messages and provide you useful information.

    https://www.microsoft.com/en-us/download/details.aspx?id=12493

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, June 09, 2016 2:27 AM
    Moderator
  • ...also the current Insider Build Windows Mobile 10.0.14364.0 has the same issue.
    The case at Microsoft Connect was closed and it was transferred to the Windows Platform team.

    Best regards

    Wednesday, June 15, 2016 11:11 PM
  • It is at least now documented as not working in 10.0.14364.0 - deploying from VS 2015  Update 2 to Mobile is currently broken, but WinAppDeployCmd works. Maybe they'll fix it.

    A

    Thursday, June 16, 2016 7:55 AM
  • With the current update 10.0.14367 this issue is fixed.
    Thank you to the Windows Mobile Platform team!

    Best regards,
    RoDi

    • Proposed as answer by RoDiPa Thursday, June 23, 2016 9:52 AM
    • Marked as answer by amacadabra Thursday, June 23, 2016 10:16 AM
    Friday, June 17, 2016 8:34 AM