You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by Tucsonjhall <Jh...@cactusware.com> on 2016/01/26 23:28:27 UTC

Oauth in authoring vs. release version of AIR program

I'm not finding anything about this but I may well not know the proper search
terms. I'm implementing oAuth using StageWebView object and it works fine in
Flash Builder debug 

https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0

but as soon as I compile a release version of the program, this is what I
see as a user

https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0

Any suggestions about how to overcome this? 

Thanks



--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Oauth in authoring vs. release version of AIR program

Posted by Tucsonjhall <Jh...@cactusware.com>.
Thanks for checking in Alex. However, using StageWebView, though I'm not
sure that would help since this it's essentially carving out a window above
all display objects and presenting the HTML it receives. Am I incorrect on
that? It's a head scratcher for me.

On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
ml-node+s2333346n11826h94@n4.nabble.com> wrote:

> Did you check that the logo is deployed with the release version?  The
> release version usually goes in a different folder from the debug version
> and maybe some asset isn't being copied.
>
> -Alex
>
> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
>
> >I'm not finding anything about this but I may well not know the proper
> >search
> >terms. I'm implementing oAuth using StageWebView object and it works fine
> >in
> >Flash Builder debug
> >
> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
> >
> >but as soon as I compile a release version of the program, this is what I
> >see as a user
> >
> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
> >
> >Any suggestions about how to overcome this?
> >
> >Thanks
> >
> >
> >
> >--
> >View this message in context:
> >
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-relea
> >se-version-of-AIR-program-tp11824.html
> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11826.html
> To unsubscribe from Oauth in authoring vs. release version of AIR program, click
> here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218MTE4MjR8LTE3MTU2NjQyODY=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
John Hall
jhall@cactusware.com
http://www.cactusware.com




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11827.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Oauth in authoring vs. release version of AIR program

Posted by Tucsonjhall <Jh...@cactusware.com>.
Thanks much for your comments. Your info is helpful and interesting.

Now I'm confused, l try the release version on my Mac and it's fine. I
don't think it's specific to my Windows computer since others see the same
thing (small sample of three different people but all Windows 10).

On Wed, Jan 27, 2016 at 2:20 AM, Christofer Dutz [via Apache Flex Users] <
ml-node+s2333346n11833h11@n4.nabble.com> wrote:

> I recently implemented a KeycloakWebService (WebService object that
> transparently handles OAuth with Keycloack).
> While at it I had a lot of similar problems. In the end the most helpfull
> tool was deffinitely Wireshark. With this I simply recorded the IP traffic
> and had a look at what was going over the wire.
>
> Some thoughts to your problems:
> 1. Eventually the resources in the loaded HTML are referenced badly (you
> should see the 404 responses in the Wireshark trace)
> 2. Eventually there is a sandbox problem. If the CSS or Image data is
> loaded from a different domain, this could be a problem (In this case you
> won't even see the http request being sent to the server)
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11833&i=0>]
> Gesendet: Mittwoch, 27. Januar 2016 07:31
> An: [hidden email] <http:///user/SendEmail.jtp?type=node&node=11833&i=1>
> Betreff: Re: Oauth in authoring vs. release version of AIR program
>
> Sure, lots of stuff is messed up, but I would start with something easy:
> why is the image not loading?  The other issues may be related.  Verify
> the files are where they should be.  Also maybe try a network monitor to
> see what URL it thinks it is trying to fetch for the logo.
>
> -Alex
>
> On 1/26/16, 9:44 PM, "Tucsonjhall" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11833&i=2>> wrote:
>
> >Plus it's certainly not just the graphic. All the CSS seems totally
> >disregarded to me.
> >
> >On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
> >[hidden email] <http:///user/SendEmail.jtp?type=node&node=11833&i=3>>
> wrote:
> >
> >> Did you check that the logo is deployed with the release version?
> >>The  release version usually goes in a different folder from the debug
> >>version  and maybe some asset isn't being copied.
> >>
> >> -Alex
> >>
> >> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
> >> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
> >>
> >> >I'm not finding anything about this but I may well not know the
> >> >proper search terms. I'm implementing oAuth using StageWebView
> >> >object and it works
> >>fine
> >> >in
> >> >Flash Builder debug
> >> >
> >> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
> >> >
> >> >but as soon as I compile a release version of the program, this is
> >>what I
> >> >see as a user
> >> >
> >> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
> >> >
> >> >Any suggestions about how to overcome this?
> >> >
> >> >Thanks
> >> >
> >> >
> >> >
> >> >--
> >> >View this message in context:
> >> >
> >>
> >>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-r
> >>ele
> >>a
> >> >se-version-of-AIR-program-tp11824.html
> >> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
> >>
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> >> discussion
> >> below:
> >>
> >>
> >>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-r
> >>ele ase-version-of-AIR-program-tp11824p11826.html
> >> To unsubscribe from Oauth in authoring vs. release version of AIR
> >>program, click  here
> >>
> >><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>
> >>macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218
> >>MTE
> >>4MjR8LTE3MTU2NjQyODY=>
> >> .
> >> NAML
> >>
> >><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>
> >>macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.n
> >>aml
> >>.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na
> >>bbl
> >>e.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nab
> >>ble
> >>%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%
> >>21n
> >>abble%3Aemail.naml>
> >>
> >
> >
> >
> >--
> >John Hall
> >[hidden email] <http:///user/SendEmail.jtp?type=node&node=11833&i=4>
> >http://www.cactusware.com
> >
> >
> >
> >
> >--
> >View this message in context:
> >http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-re
> >lea se-version-of-AIR-program-tp11824p11828.html
> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11833.html
> To unsubscribe from Oauth in authoring vs. release version of AIR program, click
> here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218MTE4MjR8LTE3MTU2NjQyODY=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
John Hall
jhall@cactusware.com
http://www.cactusware.com




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11835.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

RE: Oauth in authoring vs. release version of AIR program

Posted by Tucsonjhall <Jh...@cactusware.com>.
And to further complicate things (or actually saves time) I’ve updated to
4.15 and AIR 20 and at least it now does it in authoring mode too, so I
don’t need to compile a release version to get it to act up.



Thanks much for your comments. Your info is helpful and interesting.



Now I'm confused, l try the release version on my Mac and it's fine. I
don't think it's specific to my Windows computer since others see the same
thing (small sample of three different people but all Windows 10).



On Wed, Jan 27, 2016 at 2:20 AM, Christofer Dutz [via Apache Flex Users] <
ml-node+s2333346n11833h11@n4.nabble.com> wrote:

I recently implemented a KeycloakWebService (WebService object that
transparently handles OAuth with Keycloack).
While at it I had a lot of similar problems. In the end the most helpfull
tool was deffinitely Wireshark. With this I simply recorded the IP traffic
and had a look at what was going over the wire.

Some thoughts to your problems:
1. Eventually the resources in the loaded HTML are referenced badly (you
should see the 404 responses in the Wireshark trace)
2. Eventually there is a sandbox problem. If the CSS or Image data is
loaded from a different domain, this could be a problem (In this case you
won't even see the http request being sent to the server)

Chris

-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:[hidden email]
<http://user/SendEmail.jtp?type=node&node=11833&i=0>]
Gesendet: Mittwoch, 27. Januar 2016 07:31
An: [hidden email] <http://user/SendEmail.jtp?type=node&node=11833&i=1>
Betreff: Re: Oauth in authoring vs. release version of AIR program

Sure, lots of stuff is messed up, but I would start with something easy:
why is the image not loading?  The other issues may be related.  Verify the
files are where they should be.  Also maybe try a network monitor to see
what URL it thinks it is trying to fetch for the logo.

-Alex

On 1/26/16, 9:44 PM, "Tucsonjhall" <[hidden email]
<http://user/SendEmail.jtp?type=node&node=11833&i=2>> wrote:


>Plus it's certainly not just the graphic. All the CSS seems totally
>disregarded to me.
>
>On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
>[hidden email] <http://user/SendEmail.jtp?type=node&node=11833&i=3>>
wrote:
>
>> Did you check that the logo is deployed with the release version?
>>The  release version usually goes in a different folder from the debug
>>version  and maybe some asset isn't being copied.
>>
>> -Alex
>>
>> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=11826&i=0
<http://user/SendEmail.jtp?type=node&node=11826&i=0>>> wrote:
>>
>> >I'm not finding anything about this but I may well not know the
>> >proper search terms. I'm implementing oAuth using StageWebView
>> >object and it works
>>fine
>> >in
>> >Flash Builder debug
>> >
>> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
>> >
>> >but as soon as I compile a release version of the program, this is
>>what I
>> >see as a user
>> >
>> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
>> >
>> >Any suggestions about how to overcome this?
>> >
>> >Thanks




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11839.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

AW: Oauth in authoring vs. release version of AIR program

Posted by Christofer Dutz <ch...@c-ware.de>.
I recently implemented a KeycloakWebService (WebService object that transparently handles OAuth with Keycloack).
While at it I had a lot of similar problems. In the end the most helpfull tool was deffinitely Wireshark. With this I simply recorded the IP traffic and had a look at what was going over the wire. 

Some thoughts to your problems:
1. Eventually the resources in the loaded HTML are referenced badly (you should see the 404 responses in the Wireshark trace)
2. Eventually there is a sandbox problem. If the CSS or Image data is loaded from a different domain, this could be a problem (In this case you won't even see the http request being sent to the server)

Chris

-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com] 
Gesendet: Mittwoch, 27. Januar 2016 07:31
An: users@flex.apache.org
Betreff: Re: Oauth in authoring vs. release version of AIR program

Sure, lots of stuff is messed up, but I would start with something easy:
why is the image not loading?  The other issues may be related.  Verify the files are where they should be.  Also maybe try a network monitor to see what URL it thinks it is trying to fetch for the logo.

-Alex

On 1/26/16, 9:44 PM, "Tucsonjhall" <Jh...@cactusware.com> wrote:

>Plus it's certainly not just the graphic. All the CSS seems totally 
>disregarded to me.
>
>On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
>ml-node+s2333346n11826h94@n4.nabble.com> wrote:
>
>> Did you check that the logo is deployed with the release version?  
>>The  release version usually goes in a different folder from the debug 
>>version  and maybe some asset isn't being copied.
>>
>> -Alex
>>
>> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email] 
>> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
>>
>> >I'm not finding anything about this but I may well not know the 
>> >proper search terms. I'm implementing oAuth using StageWebView 
>> >object and it works
>>fine
>> >in
>> >Flash Builder debug
>> >
>> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
>> >
>> >but as soon as I compile a release version of the program, this is
>>what I
>> >see as a user
>> >
>> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
>> >
>> >Any suggestions about how to overcome this?
>> >
>> >Thanks
>> >
>> >
>> >
>> >--
>> >View this message in context:
>> >
>> 
>>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-r
>>ele
>>a
>> >se-version-of-AIR-program-tp11824.html
>> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the 
>> discussion
>> below:
>>
>> 
>>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-r
>>ele ase-version-of-AIR-program-tp11824p11826.html
>> To unsubscribe from Oauth in authoring vs. release version of AIR 
>>program, click  here
>> 
>><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>>macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218
>>MTE
>>4MjR8LTE3MTU2NjQyODY=>
>> .
>> NAML
>> 
>><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>>macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.n
>>aml 
>>.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na
>>bbl 
>>e.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nab
>>ble 
>>%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%
>>21n
>>abble%3Aemail.naml>
>>
>
>
>
>--
>John Hall
>jhall@cactusware.com
>http://www.cactusware.com
>
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-re
>lea se-version-of-AIR-program-tp11824p11828.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.


Re: Oauth in authoring vs. release version of AIR program

Posted by Alex Harui <ah...@adobe.com>.
Sure, lots of stuff is messed up, but I would start with something easy:
why is the image not loading?  The other issues may be related.  Verify
the files are where they should be.  Also maybe try a network monitor to
see what URL it thinks it is trying to fetch for the logo.

-Alex

On 1/26/16, 9:44 PM, "Tucsonjhall" <Jh...@cactusware.com> wrote:

>Plus it's certainly not just the graphic. All the CSS seems totally
>disregarded to me.
>
>On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
>ml-node+s2333346n11826h94@n4.nabble.com> wrote:
>
>> Did you check that the logo is deployed with the release version?  The
>> release version usually goes in a different folder from the debug
>>version
>> and maybe some asset isn't being copied.
>>
>> -Alex
>>
>> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
>>
>> >I'm not finding anything about this but I may well not know the proper
>> >search
>> >terms. I'm implementing oAuth using StageWebView object and it works
>>fine
>> >in
>> >Flash Builder debug
>> >
>> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
>> >
>> >but as soon as I compile a release version of the program, this is
>>what I
>> >see as a user
>> >
>> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
>> >
>> >Any suggestions about how to overcome this?
>> >
>> >Thanks
>> >
>> >
>> >
>> >--
>> >View this message in context:
>> >
>> 
>>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-rele
>>a
>> >se-version-of-AIR-program-tp11824.html
>> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> 
>>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-rele
>>ase-version-of-AIR-program-tp11824p11826.html
>> To unsubscribe from Oauth in authoring vs. release version of AIR
>>program, click
>> here
>> 
>><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>>macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218MTE
>>4MjR8LTE3MTU2NjQyODY=>
>> .
>> NAML
>> 
>><http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?
>>macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml
>>.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabbl
>>e.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble
>>%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21n
>>abble%3Aemail.naml>
>>
>
>
>
>-- 
>John Hall
>jhall@cactusware.com
>http://www.cactusware.com
>
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-relea
>se-version-of-AIR-program-tp11824p11828.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.


Re: Oauth in authoring vs. release version of AIR program

Posted by Tucsonjhall <Jh...@cactusware.com>.
Plus it's certainly not just the graphic. All the CSS seems totally
disregarded to me.

On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
ml-node+s2333346n11826h94@n4.nabble.com> wrote:

> Did you check that the logo is deployed with the release version?  The
> release version usually goes in a different folder from the debug version
> and maybe some asset isn't being copied.
>
> -Alex
>
> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
>
> >I'm not finding anything about this but I may well not know the proper
> >search
> >terms. I'm implementing oAuth using StageWebView object and it works fine
> >in
> >Flash Builder debug
> >
> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
> >
> >but as soon as I compile a release version of the program, this is what I
> >see as a user
> >
> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
> >
> >Any suggestions about how to overcome this?
> >
> >Thanks
> >
> >
> >
> >--
> >View this message in context:
> >
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-relea
> >se-version-of-AIR-program-tp11824.html
> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11826.html
> To unsubscribe from Oauth in authoring vs. release version of AIR program, click
> here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218MTE4MjR8LTE3MTU2NjQyODY=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
John Hall
jhall@cactusware.com
http://www.cactusware.com




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11828.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Oauth in authoring vs. release version of AIR program

Posted by Tucsonjhall <Jh...@cactusware.com>.
Another interesting fact that I just discovered. It works fine on my Mac.
It appears to be a Windows 10 thing. mmmm.

On Tue, Jan 26, 2016 at 10:07 PM, Alex Harui [via Apache Flex Users] <
ml-node+s2333346n11826h94@n4.nabble.com> wrote:

> Did you check that the logo is deployed with the release version?  The
> release version usually goes in a different folder from the debug version
> and maybe some asset isn't being copied.
>
> -Alex
>
> On 1/26/16, 2:28 PM, "Tucsonjhall" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11826&i=0>> wrote:
>
> >I'm not finding anything about this but I may well not know the proper
> >search
> >terms. I'm implementing oAuth using StageWebView object and it works fine
> >in
> >Flash Builder debug
> >
> >https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
> >
> >but as soon as I compile a release version of the program, this is what I
> >see as a user
> >
> >https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
> >
> >Any suggestions about how to overcome this?
> >
> >Thanks
> >
> >
> >
> >--
> >View this message in context:
> >
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-relea
> >se-version-of-AIR-program-tp11824.html
> >Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11826.html
> To unsubscribe from Oauth in authoring vs. release version of AIR program, click
> here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11824&code=SmhhbGxAY2FjdHVzd2FyZS5jb218MTE4MjR8LTE3MTU2NjQyODY=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
John Hall
jhall@cactusware.com
http://www.cactusware.com




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-release-version-of-AIR-program-tp11824p11829.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Oauth in authoring vs. release version of AIR program

Posted by Alex Harui <ah...@adobe.com>.
Did you check that the logo is deployed with the release version?  The
release version usually goes in a different folder from the debug version
and maybe some asset isn't being copied.

-Alex

On 1/26/16, 2:28 PM, "Tucsonjhall" <Jh...@cactusware.com> wrote:

>I'm not finding anything about this but I may well not know the proper
>search
>terms. I'm implementing oAuth using StageWebView object and it works fine
>in
>Flash Builder debug
>
>https://www.dropbox.com/s/lizo9bm6w9j5i4s/oauthAuthoring.jpg?dl=0
>
>but as soon as I compile a release version of the program, this is what I
>see as a user
>
>https://www.dropbox.com/s/b445nc32oi5f019/oauthRelease.jpg?dl=0
>
>Any suggestions about how to overcome this?
>
>Thanks
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Oauth-in-authoring-vs-relea
>se-version-of-AIR-program-tp11824.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.