This content has been marked as final.
Show 4 replies
-
1. Re: allowBrowserInvocation AIR 1.5
Joe ... Ward Jan 14, 2009 10:33 AM (in response to Damon Edwards)When I open the default app descriptor created by Flash, I see that there is already a <allowBrowserInvocation> element set to false. Most likely, you need to change the value of that element to true instead of adding a second element. -
2. Re: allowBrowserInvocation AIR 1.5
Damon Edwards Jan 14, 2009 10:55 AM (in response to Joe ... Ward)that's what strange, the first one I posted is the exact application descriptor that is generated for my app!! Now, I think it may have to do with the fact that I started using flash cs3 AIR 1.0, then migrated to flash cs4 AIR 1.5. I already had a major problem with the migration having to do with the ComponentShim. Got that fixed, although my app takes a few minutes to publish, when in cs3 it took only seconds.
What do you suggest I do, create a new AIR file, publish, then copy the app descriptor and change the values to my own??? -
3. Re: allowBrowserInvocation AIR 1.5
Damon Edwards Jan 14, 2009 11:52 AM (in response to Damon Edwards)got it working by doing: "create a new AIR file, publish, then copy the app descriptor and change the values to my own???" -
4. Re: allowBrowserInvocation AIR 1.5
Damon Edwards Jan 14, 2009 11:54 AM (in response to Damon Edwards)the move from Flash CS3 to Flash CS4 is a rough one, and all the kinks still aren't out.



