Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-23217] Windows: Packaging for dist-winstore with 8.1 SDK fails

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2016-04-20T14:56:18.000+0000
Affected Version/sRelease 5.3.0
Fix Version/sRelease 5.3.0
ComponentsWindows
Labelsqe-5.3.0, regression
ReporterEwan Harris
AssigneeChristopher Williams
Created2016-04-14T18:24:54.000+0000
Updated2016-04-20T14:56:22.000+0000

Description

Description

When attempting to package an app for dist-winstore using the 8.1 Windows SDK the build will fail with the error below
[ERROR] C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Package.appxmanifest(39,10): error APPX1674: App manifest defines lock screen notifications without specifying one of appropriate background task types: timer, control channel, push notification, or location. [C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Pkgtest.vcxproj]
[ERROR] "C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Pkgtest.vcxproj.metaproj" (default target) (2) ->
"C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Pkgtest.vcxproj" (default target) (6) ->
(_ValidateAppxManifest target) ->
  C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Package.appxmanifest(39,10): error APPX1674: App manifest defines lock screen notifications without specifying one of appropriate background task types: timer, control channel, push notification, or location. [C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Pkgtest.vcxproj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:14.76
*This is a regression from 5.2.2.GA*

Steps to reproduce

1. Package an application using appc run -p windows -T dist-winstore or appc run -p windows -T dist-winstore --wp-sdk 8.1

Actual result

The app fails to package with the error above

Expected result

The app should successfully package

Comments

  1. Christopher Williams 2016-04-15

    Weird, never ran into this before. I'm guess maybe this is related? https://social.msdn.microsoft.com/Forums/vstudio/en-US/f0339531-123d-4764-927d-8ed9251ce65a/why-do-i-have-to-specify-a-background-task?forum=csharpgeneral It's possible the app you used had an app image that we could use for a badge, so we generated one and stuck a reference to it in the manifest and then Windows went nuts thinking that meant you had a background task? Can you attach/paste the contents of C:\Users\Ewan\.titanium\vsbuild\pkgtest\store.x86\Package.appxmanifest ?
  2. Christopher Williams 2016-04-15

    [~eharris] So I put up a PR for the fix, but I'm not 100% sure if this will do it or not. One easy way to test out if it will is to edit the package manifest template we use for 8.1 store apps. In the SDK's windows/templates/build/Package.store.appxmanifest.in.ejs file, remove the line:
               <m2:LockScreen Notification="badge" BadgeLogo="Square24x24Logo.png" />
       
    And then try and clean/rebuild the project and see if that fixes it. If so, the PR fix should work.
  3. Ewan Harris 2016-04-18

    Verified using: Windows 10 Pro Visual Studio 2015 Community Update 2 Appc Core: 5.3.0-18 Appc NPM: 4.2.5-2 Ti SDK: 5.3.0.v20160418111755 Appc Studio: 4.6.0.201604180847 When packaging using appc run -p windows -T dist-winstore --wp-sdk 8.1 the appxbundle is now successfully created. Closing ticket

JSON Source