You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Fréderic Cox (JIRA)" <ji...@apache.org> on 2013/04/08 17:27:17 UTC
[jira] [Commented] (FLEX-33479) Conflict between
and captiveruntime packaging of AIR application
[ https://issues.apache.org/jira/browse/FLEX-33479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625458#comment-13625458 ]
Fréderic Cox commented on FLEX-33479:
-------------------------------------
Possible workaround is to use the NativeProcess API and start the application just before closing itself. I did this and it worked.
> Conflict between <allowBrowserInvocation> and captiveruntime packaging of AIR application
> -----------------------------------------------------------------------------------------
>
> Key: FLEX-33479
> URL: https://issues.apache.org/jira/browse/FLEX-33479
> Project: Apache Flex
> Issue Type: Bug
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: ALL
> Reporter: Abhishek Dwevedi
> Labels: adt, air, allowbrowser, captiveruntime, packaging
>
> Hi Team,
> I am trying to create an air app to reboot itself, its running fine with native installer or signed package but when i package it using captive runtime its throws issues
> Case 1:
> Packagin by Captive Runtime
> <allowBrowserInvocation>true<allowBrowserInvocation
> Issue "Browsers invocation is not supported for this target"
> Case 2:
> Packagin by Captive Runtime
> <allowBrowserInvocation>false<allowBrowserInvocation
> Application Doesn't works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira