Bot-docs: notify not working

[abhi23arora]

The following error occurs whenever this url is hit http://localhost:3978/api/notify
Unable to resolve service for type 'Microsoft.Bot.Connector.Authentication.ICredentialProvider' while attempting to activate 'ProactiveBot.Controllers.NotifyController'.

System.InvalidOperationException: Unable to resolve service for type 'Microsoft.Bot.Connector.Authentication.ICredentialProvider' while attempting to activate 'ProactiveBot.Controllers.NotifyController'.

at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, Boolean isDefaultParameterRequired)

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 521a9f9a-025c-c55b-c939-d9d4efc5c6d0
• Version Independent ID: 3bcafb54-f7eb-54f5-1d78-5f2087e2e2dc
• Content: Send proactive notifications to users - Bot Service
• Content Source: articles/v4sdk/bot-builder-howto-proactive-message.md
• Service: bot-service
• Sub-service: sdk
• GitHub Login: @JonathanFingold
• Microsoft Alias: jonathanfingold

[Romanski1]

bot-docs/botframework-config

[markolb81]

I implemented the scenario above for MS Teams Channel specifically where I store serialized conversation references to send a proactive message via "ContinueConversationAsync".
After some time, I realized that after some time, the stored conversation reference does not work any more, the conversation is not being resumed.
Is there a timeout / expiration date for conversation references? Is there a way, to actually start a 1:1 conversation within teams?

[tdurnford]

Have you tried enabling trust service urls in your project? Take a look at he Send proactive notifications to users documentation and let me know if that resolves your issue.

[CoHealer]

@markolb81, do you still need assistance?

[markolb81]

Hi CoHealer, I wasn't unable to test until now - I added this specific line of code to trust that URL, first test seems to be good - thanks for that!

[markolb81]

A related issue: I know that it's on the roadmap to provide a real proactive messaging for the MS Teams Channel, but until then: do you see any workaround to generate conversation references for users that did not contacted the bot themselves? What about using some sort of powershell, that impersonates to every user within the Active Directory and once sends a short activity to the bot to initiate a conversation reference that I can then store? Will this work?

[mdrichardson]

@markolb81 Yes, you can do that.

Basically, you:

1. Fetch the Team Roster

2. Start a Proactive Conversation

You'll likely find this StackOverflow answer helpful.

[mdrichardson]

@markolb81 As your original issue was resolved, I'm going to close this. If you run into trouble trying to implement my previous comment, feel free to open a Stack Overflow issue.