Expand my Community achievements bar.

SOLVED

Using AFCS SDK with Gumbo

Avatar

Former Community Member

Hi,


is there a way to start using the sdk with actual gumbo sdk builds?

I'am running into strange errors. Or is this not supported at this time?

Thanks for any infos or workarounds.

Cheers, Sven

1 Accepted Solution

Avatar

Correct answer by
Level 1

Hi Sven,

Is your AdobeHSAuthenticator in a Declarations tag ?

In Gumbo, all non visual elements must be in the Declarations tag.

Romain

View solution in original post

7 Replies

Avatar

Former Community Member

Hi Sven,

  We definitely had tried at some point without problems, but we haven't been keeping up with the latest Gumbo builds - what kinds of errors are you seeing? We can look into them and hopefully get them fixed for the next drop.

  thanks

   nigel

Avatar

Former Community Member

Hi Nigel,

thanks for your help.

At the moment it fails in a very early stage only by describing the AdobeHSAuthenticator.

This class ist also not in the code completion by adding the correct 'rtc' namespace.

Description    Resource    Path    Location    Type
In initializer for 'mxmlContentFactory', type com.adobe.rtc.authentication.AdobeHSAuthenticator is not assignable to target type Array or target element type mx.core.IVisualElement.    AFCS_Demo01.mxml    AFCS_Demo01/src    line 14    Flex Problem

Any idea?

Thanks, Sven

Avatar

Correct answer by
Level 1

Hi Sven,

Is your AdobeHSAuthenticator in a Declarations tag ?

In Gumbo, all non visual elements must be in the Declarations tag.

Romain

Avatar

Former Community Member

Another possible way to workaround this would be the form I happen to prefer for Authenticating :

<rtc:ConnectSessionContainer ... >

<rtc:authenticator> <rtc:AdobeHSAuthenticator ... /> </rtc:authenticator> </rtc:ConnectSessionContainer>

nigel

Avatar

Former Community Member

Damn Sorry heavily switching between SDK 3.x and 4.x and i forgot that <Declaration/> Tag.

Thanks for the hint!

Cheers, Sven

Avatar

Former Community Member

Hi Nigel,

why you prefer this way?

What is the difference or advantages not seperately define the Authenticator?

Thanks, Sven

Avatar

Former Community Member

I like it because you don't have to name the Authenticator with an id property, and you don't have to bind in the authenticator w/ curlies. I guess I just like the purity of having the session "contain" the authenticator.

nigel