CoBrowse not working on android devices with API level 23 or above

[edwin.ramana]

We've installed REAS and REMB in our lab.

We're using expert_assist_android_SDK-11.5.1.10000-22

We are working on re mobile android sdk integration, now we are facing issue when using co browse feature with android devices with API level 23(marshmallow) or above. The feature is working fine on api level 22(lolipop 5.1). But when i tried it on marshmallow devices, it only showed a vertical line.

Any idea how to fix it? thx in advance.

[rdavies1]

Cheers Edwin,

Can you share your own code you've edited from the sample shown on: https://developer.cisco.com/media/remote-expert-mobile-developer-tutorials/android-sdk/10-restricted-client-access/restr…

Cheers,

Rach

[edwin.ramana]

Hi Rach,

This is the project

REM1 - Google Drive

Cheers,

Edwin

[edwin.ramana]

I changed Anonymous Consumer Access into disabled and it worked fine on web sdk using sessionID but it doesnt work on android sdk.

Cheers,

Edwin

[rdavies1]

Hi Edwin.

That is strange, authentication should be working for Android also. I will look into this and make sure there is no defects.

You mentioned call was setting up before you applied this, can you confirm if co-browse was also working too? Given that was the original issue of the thread? If so what did you change to get it working again?

Cheers,

Rach

[edwin.ramana]

I'm  using the latest patch 11.5.1.10000-22.ES4

Yes, it was working fine before. But after I use authentication, it's not working.

The co browse is still not working but I need to fix this problem first because it's more important or should I make a new thread about this problem?

Cheers,

Edwin

[rdavies1]

Thanks for clarifying.

I think that would be a good idea, we can keep the two separate and easier to manage then.

If you could grab some logs with the auth off for this thread then we can take a look at the co-browse issue too.

Cheers,

Rach

[edwin.ramana]

Ok, i've made new thread about this problem

We can use that thread to discuss this problem.

We can continue to discuss the co browse problem later on this thread when the authentication problem solved.

Cheers,

Edwin