Page 2 of 3
Re: Windows Store Build
Posted: 06 Sep 2015, 15:08
by Scherub
Are you sure it's a good idea to post this link here?
Edit: Btw I have the same problem with WinStore and WinPhone builds.
Re: Windows Store Build
Posted: 06 Sep 2015, 15:23
by jsantos
Are you it's a good idea to post this link here?
I have removed the link and moved it to the tracker. Thanks for notifying!
Edit: Btw I have the same problem with WinStore and WinPhone builds.
The patching problem?
There are two problems here, one is the automatic patching we implemented in 1.2.4, it seems it is not working properly. The second one is related to UTF8, it seems that Mono and Microsoft CLR behaves differently when passing strings from c# to c++. We are investigating it.
Re: Windows Store Build
Posted: 06 Sep 2015, 17:07
by picpic2006
Thanks to moved the file, no it was surely not a good idee !
I didn't realise that i give the plugin with !
Sorry
Re: Windows Store Build
Posted: 06 Oct 2015, 17:10
by picpic2006
Hello,
I have come to hear yours news for the UTF8 problem related here, have you investigate ?
Thanks you
Re: Windows Store Build
Posted: 06 Oct 2015, 22:57
by jsantos
The patching problem is planned to be solved in the next release. Anyway, there is an easy workaround for it.
The UTF8 problem is more complex, we have it under control, but we don't know yet if it will go in v1.2.5 or v1.2.6. How critical is it for you?
Thanks for your patience!
Re: Windows Store Build
Posted: 07 Oct 2015, 09:39
by picpic2006
It become critical, because my app autorise user text input and i have accent bug, i can wait for the next release !
Thanks you
Re: Windows Store Build
Posted: 07 Oct 2015, 19:26
by jsantos
The workaround for the "Failed to patch file" error is applying the following changes to NoesisBuildPostprocessor.cs
--- NoesisBuildPostprocessor.cs (revision 5585)
+++ NoesisBuildPostprocessor.cs (working copy)
@@ -18,13 +18,19 @@
private static void OnPostprocessBuildWSA(string pathToBuiltProject)
{
string exportedPath = Path.Combine(pathToBuiltProject, PlayerSettings.productName);
- string[] filesToSearch = new[] { "App.xaml.cs", "MainPage.xaml.cs" };
+ string[] filesToSearch = new[]
+ {
+ "App.xaml.cs",
+ "MainPage.xaml.cs",
+ Path.Combine(PlayerSettings.productName + ".Shared", "App.xaml.cs"),
+ Path.Combine(PlayerSettings.productName + ".Shared", "MainPage.xaml.cs")
+ };
Re: Windows Store Build
Posted: 02 Nov 2015, 18:53
by picpic2006
Hi,
I just created the ticket in bug tracker for the utf8 convertion problem.
I hope you will be able to correct it soon.
Thanks you
Re: Windows Store Build
Posted: 01 Dec 2015, 17:06
by picpic2006
Hello,
Is the bug concerning utf8 will be solve for the next version and when it will be available, It really become urgent.
My client ask me why accent are not supported.
Thanks you
Re: Windows Store Build
Posted: 01 Dec 2015, 20:11
by jsantos
Yes, it will be solved for the next version. But right now, I cannot give a release date. The plan is having it ready in 4 weeks.
There is a workaround though. If you store the text in the XAML (as a resource for example) then the utf8 will work fine. The only problem is when the strings are being passed from C# (because Microsoft CLR handles unicode differently from Mono).
Is this a valid workaround for you?