[TIMOB-26311] Windows: leverage extended execution restricted capabilities
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2018-08-20T23:42:21.000+0000 |
Affected Version/s | Release 7.3.0 |
Fix Version/s | Release 7.5.0 |
Components | Windows |
Labels | n/a |
Reporter | Riduanul Islam |
Assignee | Kota Iguchi |
Created | 2018-08-16T19:08:17.000+0000 |
Updated | 2018-09-12T09:59:27.000+0000 |
Description
Hello,
One a Windows App with Appcelerator which calls an asynchronous function on a .NET Core SDK which downloads extensive amounts of data and saves it directly on the App's AppData however, as per limitations from Windows 10, the App must be in the foreground for the whole execution.
This creates a problem because if the App gets minimized or it is unfocused while on FullScreenMode, this call will fail. There exists a few restricted capabilities in UWP that may help with this and I wanted to reach out whether these are supported on Ti SDK 7.3 for Windows 10 or whether there's a way to do this within the Titanium SDK.
The customer have tried adding
...
On the tiapp.xml file however, in the vsbuild folder's manifest these were removed. They also tried prefixing the Capability element with rescap but it failed to compile.
Please let us know if you need any more information.
Thanks
https://github.com/appcelerator/titanium_mobile_windows/pull/1281
It failed because the
appxmanifest
XML doesn't haverescap
namespace. We have merged the fix in master (https://github.com/appcelerator/titanium_mobile_windows/pull/1281/files). With the fix,rescap
Capabilities can be defined like below.Thanks for the information. We have shared the information with the customer regarding this Fix.
*Closing ticket.* Verified improvement in SDK Version
7.5.0.v20180911212648
.rescap
capabilities can now be defined without the application throwing an error. *Test Steps (FR Passed):*Created a new titanium application
Added the following in to the
Tiapp.xml
Ran the app using
appc run -p windows --build-only
Application was able to build without an errors
*Test Environment*