Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release build for Device failing on Windows Phone 8.1 WinRT #428

Closed
camilomartinez opened this issue Jun 15, 2015 · 10 comments
Closed

Release build for Device failing on Windows Phone 8.1 WinRT #428

camilomartinez opened this issue Jun 15, 2015 · 10 comments

Comments

@camilomartinez
Copy link

I am facing an issue while building a WP 8.1 WinRT application using Humanizer. It only happens when using Release configuration for an actual device not an emulator. The build error I receive is

Error : DEP6810 : MdilXapCompile.exe failed with error code 1004.
See log file '...\obj\Release\MDIL\MDILXapCompileLog.txt' for more details.

The only useful line in that log contains:

Error: Compile filter argument specified non-existent file:
...\obj\Release\MSIL\af\Humanizer.resources.dll
Invalid argument

which points out to an issue with resources in Humanizer. The error seems to be similar to one mention in this other app issue (RateMyApp Issue #45) which makes me think it might be related with using resources from a PCL.

Are you aware of this issue? Anyone else facing it?

@MehdiK
Copy link
Member

MehdiK commented Jun 21, 2015

Thanks for reporting the issue @camilomartinez. This is the first time I'm seeing this error. You're right. It seems to be the same issue reported here. The suggested solution sounds a bit strange. I will see what can be done.

@pedropombeiro
Copy link

FWIW, I'm also facing this issue. I'm compiling Debug for an actual device.

@MehdiK
Copy link
Member

MehdiK commented Aug 17, 2015

Thanks for reporting @pombeirp.

@pedropombeiro
Copy link

Hi @MehdiK. Any news on a fix for this issue?

@MehdiK
Copy link
Member

MehdiK commented Sep 11, 2015

Haven't had the chance to look further into this @pombeirp.

@pedropombeiro
Copy link

No problem. In the meantime, I've had to remove Humanizer from our app in order to contain the crashes seen in the wild. WP can be a difficult beast :-(

@clairernovotny
Copy link
Member

So couple of thoughts here...

What version of VS is this; I assume 2013 Update 5? Is it any different with VS 2015? Do you have a consistent repro?

I'd like to get to the bottom of this. There's an open PR, #469, to split the locale's out into satellite packages but I'm not sure if that'll really fix the issue.

If there's a way to get a repro, I can dive deeper and raise the issue with the appropriate teams at Microsoft as well.

@austhomp
Copy link

The issue is actually due to the fact that MS changed how they handle resources between Windows Phone 8 and 8.1 and Universal apps. WP 8.0 and below use .resx files like we're used to, and the newer things use .resw files. Here is a nice description of the change.

Here is a MSDN Blog post about the issue and ways to work around it.

From my understanding of the proposed solution, if we know what resources are in the PCL we can load them via reflection and inject them into the main resource system. The consumers would need to do this, or maybe a separate nuget package could be provided that did that automatically. The advantage there is that the nuget can be kept in sync with any additional resource files added to Humanizer.

@clairernovotny
Copy link
Member

I can confirm this bug and have a repro here (rename to zip)
LocalizationRepro.zip.docx

Interestingly, this bug only seems to occur on VS 2013; it works fine in VS 2015. I suspect the packaging tooling (even for Win Phone 8.1 projects) changed a bit.

To be clear, this appears a tooling bug. PCL's can definitely continue to have ResX files and use the ResourceManager as those are supported in the PCL surface area.

Can you try opening/building/deploying your code in VS 2015?

@SimonCropp
Copy link
Collaborator

closing since Windows Phone is dead

@SimonCropp SimonCropp closed this as not planned Won't fix, can't repro, duplicate, stale Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants