Proactive Message using the Twitter Adapter

[hemkay]

Hi, I make use of the twitter adapter and it's working fine with my use case. However, I want to be add the proactive feature to it which keeps giving me Internal Server error whenever it reaches the twitter channel, then I discover the serviceurl from all twitter conversationReference is null. Is there a way I can send proactive message via this twitter adapter or I will need to look at other options. If other option is the way out, I will love to have your suggestions on the nest possible option to use.

Thanks

[garypretty]

@hemkay Thanks for raising the issue. I will try and take a look at this, but it may be a little time before I get chance. @arafattehsin are you able to take a look at this and help a little? I suspect the issue here could be that the Twitter adapter needs some updates to how the conversation reference is set on the way in?

[hemkay]

@garypretty, thanks. I will ne expecting an update when you can take a look, I hope @arafattehsin can take a look before then. Thanks to you both

[arafattehsin]

Hi @hemkay - thanks for reporting this. I will try my best to look into this. Meanwhile, can you please tell me if the proactive messages are working for your other channels?

[hemkay]

Hi @arafattehsin.... Yes I tested it with telegram and MS Teams and they both work fine. Thank you

[vovanb]

@arafattehsin , @garypretty I am receiving below error when calling await ((BotAdapter)_adapter).ContinueConversationAsync(_appId,_cp.ConversationReference , async (context, token) => { await context.SendActivityAsync(msgObj.message); }, default(CancellationToken));

Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer: Error: Connection ID "17293822575008284677", Request ID "80000006-0001-f000-b63f-84710c7967bb": An unhandled exception was thrown by the application.

System.ArgumentNullException: Value cannot be null. (Parameter 'clientSecret')

I tried to store ClaimsIdentity and OAuthScope but they always null in incoming request from twitter

[vovanb]

@arafattehsin, @garypretty any chance to fix this issue?