Announcement

Collapse
No announcement yet.

Unreal Engine 4 is available for Win10 UWP app dev now

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Originally posted by jsyarrow View Post
    Good catch, I was missing the -pvk switch . Here's the fixed version (plus I've edited the original for the sake of those who come after)
    That helped in making progress , thank you !
    I've got a new issue that's preventing packaging of UWP64 and UWP32 using the resulting cert. I modified the supplied command to the following:

    makecert MyCert.cer -r -n "CN=NexyMedia" -$ individual -sv MyCert.pvk -pe -cy end
    pvk2pfx -pvk MyCert.pvk -spc MyCert.cer -pfx MyCert.pfx
    Once generated, I proceed to set the result as the certificate on the UWP page. I made sure to cook for windows and that finished successfully.
    Below is the output from the editor when I try to package for UWP64. In the log it says to see 'signtool-2016.08.05-13.08.24.txt' for more details, after a thorough search of my system no such file exists.
    I'm currently packaging for UWP32 to see if I get the same result.

    [MENTION=3956]James Barnette[/MENTION]
    I did manage to get my test game to install through the device portal by uploading the UWP contents from the build folder. The splash screen started up but because there was no cooked content it crashed. Once I have the cert issue resolved I'll try it with a signed package or copy cooked content to my build folder and try that way again, though I think that signing the package may do the trick.

    MainFrameActions: Packaging (UWP (x64-64bit)): Project.Package: ********** PACKAGE COMMAND STARTED **********
    MainFrameActions: Packaging (UWP (x64-64bit)): CommandUtils.Run: Run: C:\Program Files (x86)\Windows Kits\10\bin\x64\makeappx.exe pack /o /d "C:\Users\MrNexy\Documents\Unreal Projects\UWPGM\Saved\StagedBuilds\UWP" /p "C:\Users\MrNexy\Documents\Unreal Projects\UWPGM\Saved\StagedBuilds\UWP\UWPGM.appx"
    MainFrameActions: Packaging (UWP (x64-64bit)): CommandUtils.Run: Run: Took 16.3678471s to run makeappx.exe, ExitCode=0
    MainFrameActions: Packaging (UWP (x64-64bit)): CommandUtils.Run: Run: C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe sign /a /f "C:\Users\MrNexy\Documents\Unreal Projects\UWPGM\Build\UWP\Signing Certificate.pfx" /fd SHA256 C:\Users\MrNexy\Documents\Unreal Projects\UWPGM\Saved\StagedBuilds\UWP\UWPGM.appx
    MainFrameActions: Packaging (UWP (x64-64bit)): CommandUtils.Run: Run: Took 1.053228s to run signtool.exe, ExitCode=1
    MainFrameActions: Packaging (UWP (x64-64bit)): Program.Main: ERROR: AutomationTool terminated with exception: AutomationTool.AutomationException: Command failed (Result:1): C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe sign /a /f "C:\Users\MrNexy\Documents\Unreal Projects\UWPGM\Build\UWP\Signing Certificate.pfx" /fd SHA256 C:\Users\MrNexy\Docum
    ents\Unreal Projects\UWPGM\Saved\StagedBuilds\UWP\UWPGM.appx. See logfile for details: 'signtool-2016.08.05-13.08.24.txt'
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.CommandUtils.RunAndLog(String App, String CommandLine, String Logfile, Int32 MaxSuccessCode, String Input, ERunOptions Options, Dictionary`2 EnvVars) in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\AutomationUtils\ProcessUtils.cs:line 814
    MainFrameActions: Packaging (UWP (x64-64bit)): at UWP.Automation.UWPPlatform.Package(ProjectParams Params, DeploymentContext SC, Int32 WorkingCL) in f:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\UWP\UWPPlatform.Automation.cs:line 135
    MainFrameActions: Packaging (UWP (x64-64bit)): at Project.Package(ProjectParams Params, Int32 WorkingCL) in f:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\Scripts\PackageCommand.Automation.cs:line 41
    MainFrameActions: Packaging (UWP (x64-64bit)): at BuildCookRun.DoBuildCookRun(ProjectParams Params) in f:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\Scripts\BuildCookRun.Automation.cs:line 218
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool
    MainFrameActions: Packaging (UWP (x64-64bit)): .BuildCommand.Execute() in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\AutomationUtils\BuildCommand.cs:line 28
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.Automation.Execute(List`1 CommandsToExecute, CaselessDictionary`1 Commands) in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\AutomationUtils\Automation.cs:line 538
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.Automation.Process(String[] CommandLine) in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\AutomationUtils\Automation.cs:line 509
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.Program.MainProc(Object Param) in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\Program.cs:line 131
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.InternalUtils.RunSingleInstance(Func`2 Main, Object Param) in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\AutomationUtils\Utils.cs:line 704
    MainFrameActions: Packaging (UWP (x64-64bit)): at AutomationTool.Program.Main() in F:\MICROSOFT_UWP_UNREAL\Engine\Source\Programs\AutomationTool\Program.cs:line 54
    MainFrameActions: Packaging (UWP (x64-64bit)): Program.Main: AutomationTool exiting with ExitCode=1 (Error_Unknown)
    MainFrameActions: Packaging (UWP (x64-64bit)): Domain_ProcessExit
    MainFrameActions: Packaging (UWP (x64-64bit)): AutomationToolLauncher exiting with ExitCode=1
    MainFrameActions: Packaging (UWP (x64-64bit)): copying UAT log files...
    MainFrameActions: Packaging (UWP (x64-64bit)): BUILD FAILED

    Leave a comment:


  • replied
    Has anyone sucessfully gotten something to deploy on an xbox on in dev mode yet? Dont wanna put mine back into devmode until I know there is a proven work flow for gettign it deployed.
    Hoping Unreal will perform better than unity did. it freaking crawled at like 5 FPS with a simple menu when I deployed from unity 5.

    Leave a comment:


  • replied
    Originally posted by MrNexy View Post
    A question about creating the pfx. I made a batch file using the commands provided above. Makecert pops up with a password request and I click none, after that I see the .cer and .pvk files appear in my folder. Then pvk2pfx fires off but unsuccessfully as the pfx file isn't created in the directory. There is no error message however, I'm using the (x86) versions of makecert.exe and pvk2pfx.exe from the 'Windows Kits\10\Bin' folder structure.
    Good catch, I was missing the -pvk switch . Here's the fixed version (plus I've edited the original for the sake of those who come after)

    makecert MyCert.cer -r -n "CN=My Company" -$ individual -sv MyCert.pvk -pe -cy end
    pvk2pfx -pvk MyCert.pvk -spc MyCert.cer -pfx MyCert.pfx

    Leave a comment:


  • replied
    Originally posted by jsyarrow View Post
    Turns out the Signing Certificate property had the same chicken-and-egg bug as the images. If you pull commit 2d8bed9 you should be able to provide a certificate through the UI.

    You can generate a pfx file suitable for use during development and testing using something like:


    Some notes:
    - You only need a certificate if you want to install a packaged version of your app (i.e. wrapped up as a single appx file). That's particularly useful for devices that are in the default 'Sideload apps' mode; it may be less relevant for devices in Developer Mode where you can use an unsigned version (provided you don't package it).
    - It's important that your certificate Subject name matches the Company Distinguished Name, otherwise signing will fail.
    - The current implementation doesn't support password protected certificates.
    That's handy to know. I was getting this error when trying to install a packaged UWP onto my XBO from the device portal.
    A question about creating the pfx. I made a batch file using the commands provided above. Makecert pops up with a password request and I click none, after that I see the .cer and .pvk files appear in my folder. Then pvk2pfx fires off but unsuccessfully as the pfx file isn't created in the directory. There is no error message however, I'm using the (x86) versions of makecert.exe and pvk2pfx.exe from the 'Windows Kits\10\Bin' folder structure.

    Leave a comment:


  • replied
    Turns out the Signing Certificate property had the same chicken-and-egg bug as the images. If you pull commit 2d8bed9 you should be able to provide a certificate through the UI.

    You can generate a pfx file suitable for use during development and testing using something like:
    makecert MyCert.cer -r -n "CN=My Company" -$ individual -sv MyCert.pvk -pe -cy end
    pvk2pfx -pvk MyCert.pvk -spc MyCert.cer -pfx MyCert.pfx
    Some notes:
    - You only need a certificate if you want to install a packaged version of your app (i.e. wrapped up as a single appx file). That's particularly useful for devices that are in the default 'Sideload apps' mode; it may be less relevant for devices in Developer Mode where you can use an unsigned version (provided you don't package it).
    - It's important that your certificate Subject name matches the Company Distinguished Name, otherwise signing will fail.
    - The current implementation doesn't support password protected certificates.
    Last edited by jsyarrow; 08-04-2016, 07:29 PM.

    Leave a comment:


  • replied
    Originally posted by Keresh View Post
    Of course I turn on dev mode. But I haven't signed app. And I don't know how I must sign it. I have same message as Sentinel when used Test Certification.
    This might help here you can try and sidelode the app if it is unmanaged https://technet.microsoft.com/itpro/...-in-windows-10

    Leave a comment:


  • replied
    Originally posted by towe102productions View Post
    you need to turn on dev mode on you phone to do so go here https://msdn.microsoft.com/en-us/win...or-development
    Of course I turn on dev mode. But I haven't signed app. And I don't know how I must sign it. I have same message as Sentinel when used Test Certification.

    Leave a comment:


  • replied
    [MENTION=147492]towe102productions[/MENTION]
    I have dev mode enabled, but still not able to install the app, instead its giving me following message:
    Ask the app developer for a new app package. This one isn't signed with a trusted certificate (0x800B0100)

    Leave a comment:


  • replied
    Originally posted by Keresh View Post
    Hello all.
    I have next problem.
    If I use Launch UWP button - project install and launch on my computer with Windows 10. But if I want create UWP package I have warning "No signing certificate provided. App will not be deployable. Specify a valid pfx in UWP platform settings.". After this I don't have capabilities install my package to my computer or Windows phone.
    Where can I get "signing certificate" or what is another way to start project on Windows phone without "signing certificate"?

    Sank for you work with UE4 and UWP.
    you need to turn on dev mode on you phone to do so go here https://msdn.microsoft.com/en-us/win...or-development

    Leave a comment:


  • replied
    I tried to use a Test Certification which I quickly created via a UWP test project inside of visual studio but I could not load it into the UWP Settings in unreal engine 4. Only tell me that it 'Could not override Certification file'.

    Leave a comment:


  • replied
    Hello all.
    I have next problem.
    If I use Launch UWP button - project install and launch on my computer with Windows 10. But if I want create UWP package I have warning "No signing certificate provided. App will not be deployable. Specify a valid pfx in UWP platform settings.". After this I don't have capabilities install my package to my computer or Windows phone.
    Where can I get "signing certificate" or what is another way to start project on Windows phone without "signing certificate"?

    Sank for you work with UE4 and UWP.
    Last edited by Keresh; 08-04-2016, 10:38 AM.

    Leave a comment:


  • replied
    What about the images resolution?

    <Code>
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Prepping UE4Game for deployment to UWP32
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Empty or invalid value provided for required attribute Square150x150Logo on partially specified element Package.Applications.Application[0].uap:VisualElements
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Empty or invalid value provided for required attribute Square44x44Logo on partially specified element Package.Applications.Application[0].uap:VisualElements
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Empty or invalid value provided for required attribute Image on partially specified element Package.Applications.Application[0].uap:VisualElements.uap:SplashScreen
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Validation error reading XML schema from XDK. Ԫ�� �����ռ䡰http://schemas.microsoft.com/appx/ma...es���� �����ݲ�������ӦΪ����Ԫ�ص��б�: �����ռ䡰http://schemas.microsoft.com/appx/ma...tion/windows10
    MainFrameActions: 打包 (UWP (x86-32bit)): ���еġ�Logo������
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Validation error reading XML schema from XDK. Ԫ�� �����ռ䡰http://schemas.microsoft.com/appx/ma...on���� �����ݲ�������ӦΪ����Ԫ�ص��б�: �����ռ䡰http://schemas.microsoft.com/appx/ma...ce���� �Լ� �����ռ䡰http://schemas.micro
    soft.com/appx/manifest/uap/windows10���еġ�VisualElements������
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Writing PRI config file to E:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Intermediate\Deploy\priconfig.xml ...
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Successfully Completed
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Microsoft (R) MakePRI Tool
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: Copyright (C) 2013 Microsoft. All rights reserved.
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool:
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool: MakePri: error 0x80080204: Appx manifest not found or is invalid. Please ensure well-formed manifest file is present. Or specify an index name with /in switch.
    MainFrameActions: 打包 (UWP (x86-32bit)): UnrealBuildTool:
    </Code>

    Leave a comment:


  • replied
    [MENTION=147492]towe102productions[/MENTION] I took a look at your logs. I think the main one that's relevant here is the UAT log. The error there suggests you don't have developer mode switched on in Windows 10. You'll want to follow the instructions here to get that fixed.
    [MENTION=32283]Sentinel[/MENTION] ad69f3c was an attempt to address the NetworkManifest.xml issue. If you haven't pulled that commit yet I'd recommend grabbing it and trying again. Alternatively you can place a dummy NetworkManifest.xml in Game/Config/UWP - content shouldn't matter since it's not used in this release.

    Leave a comment:


  • replied
    Thanks you [MENTION=494622]jsyarrow[/MENTION] for helping me troubleshoot the issues that I was having, I made the changes that you suggested and everything is running smoothly now.
    Now I'm setting my eye on deploying to my XBO in dev mode

    Leave a comment:


  • replied
    Hey guys,

    as I already posted on the Git I managed to get through the 'COOK COMMAND COMPLETED' but during the 'STAGE COMMAND STARTED' it failed.
    I leave the publisher information blank, I didn't receive the errors with the images, but from the looks of the logs it seems like it needs a 'Title Id' in the UWP settings so I just entered a '2'.
    After that it tells me that it could not find the 'Networking.xml'.
    Put my logs as an attachment to this post.

    Cheers
    Attached Files

    Leave a comment:

Working...
X