-
Notifications
You must be signed in to change notification settings - Fork 965
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
Comments
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. |
FWIW, I'm also facing this issue. I'm compiling Debug for an actual device. |
Thanks for reporting @pombeirp. |
Hi @MehdiK. Any news on a fix for this issue? |
Haven't had the chance to look further into this @pombeirp. |
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 :-( |
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. |
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. |
I can confirm this bug and have a repro here (rename to zip) 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? |
closing since Windows Phone is dead |
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
The only useful line in that log contains:
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?
The text was updated successfully, but these errors were encountered: