Deployment failed with error: '0x80070126' when deploying in VS

Unity Engine
,
1

I get the following message when Deploying in Visual Studio however the app deploys fine and has no issues on the device.

Deployment of application to device failed.
Deployment failed with error: ‘0x80070126’. Please try again. If the problem continues, try restarting your Windows Phone and repairing Visual Studio for Windows Phone.

The only thing I can find on google is this, and the fix was to update to the newest version of Unity. I was using 4.3.3 when I was having this problem and I’m still experiencing it on 4.3.4, though I realize that is not the Unity version they were referring to. I have also tried to repair Visual Studio and restart my phone without success, however when deploying an empty project the error doesn’t appear.

I ignored it initially since it seemingly had no impact on the build but after submitting a beta version to Microsoft I am having trouble downloading it from the store. It downloads fine but after it begins installing it says “We’re having trouble installing this app…”. I can’t help but think these issues are related.

Has anyone experienced either issue?

Notes:
Operating System: Windows 8.1
Unity Version: 4.3.3/4.3.4
Device: Nokia Lumia 520/Samsung ATIV
Visual Studio: Express 2012 for Windows Phone

2

This sounds serious. We will investigate it immediately.

EDIT: are you using GDR3 by any chance? Could you PM me the game name/download link so I could try it on devices we have?

3

Thanks I appreciate it.

I’m not sure whether I’m using GDR3, how would I check?

The OS version for the Samsung is: 8.0.10211.204 and the Nokia is on 8.0.10328.78 if that helps.

And yeah it would be awesome if you could take a look, here’s the link:

http://www.windowsphone.com/s?appid=71c7acf1-4a98-4add-9ed6-54ecbb1cc3d3

4

Thanks, I will. Is this happening on both of your devices? It says I don’t have permission to download the app, did you publish it as beta? If so, you’ll need to add my email to the list of people that can download it. Please add permission to your Unity forum account to receive messages so I could PM it to you :).

5

Sorry for the delay, I got held up. I’ll be by a computer for the next few hours though.

Yeah it is in beta, I’ll have to add you to it.

I can’t seem to find where to set my permissions though, but if you send it email it to jackson@nextgenreality.com I’ll add you

6

So I finally got to the bottom of it. Turns out Assembly-UnityScript.dll can not exceed a certain amount in size (around 9.5MB), or you receive this error message which prevents the app installing correctly when downloading from the store. I was able to take some of the unused scripts out of the project which allowed it to get under this limit.

7

Thanks for notifying. Do you mind submitting a bug illustrating this? We’d be more than glad to look into it.

8

I just hit this today. I do not have Assembly-UnityScript.dll at all and my Assembly-CSharp.dll is only 2.2 megs. I had the project working fine up until yesterday, then this suddenly begun. I am using 4.3.3 and I have the issue on two different phones (820/920), so it does not seem to be an issue with the phone.

Building and deploying a small test project from Unity also works.

Any pointers?

9

Interesting. If I deploy directly from Unity, this problem does not occur. Only if I deploy from Visual Studio. Good for deployment. Bad for testing.

10

Can you submit a bug? We would be more than glad to take a look at it.

11

The way I was able to solve it was to create an empty project and slowly add more and more of the original project building with every addition until it came up. When the error finally came up I removed one of the components that had been there for many builds before and the problem went away. I tried a bunch of different combinations of which components to keep and remove and there seemed no importance on what was kept/lost just the fact that the project was lighter script-wise. Whenever the .dll got too big (for me approximately over 9.5mb) I receive this error.

The only thing I can really recommend is a similar approach. See if removing a couple bigger scripts that have previously built successfully fixes the problem. I’d be interested to know the answer, because I’m eventually going to have to deal with it again.

@Tautvydas Zilys Sorry I meant to get back to this and forgot. I’m not sure it’s worth submitting a bug until there’s a more concrete cause of the problem. It seems it could be caused by something else as well based on fehaar’s experience.

12

That’s true, but if we can repro it using a specific project, we might be able to nail down the root issue.

13

The same message appeared to me. The problem was that my phone storage had only 992Kbytes free spasce.
I beleive if you free up some space this message will disapear.