Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic bot on mac throws error in BasicBot.cs #1218

Closed
diberry opened this issue Feb 8, 2019 · 3 comments
Closed

Basic bot on mac throws error in BasicBot.cs #1218

diberry opened this issue Feb 8, 2019 · 3 comments
Assignees
Labels
bug Indicates an unexpected problem or an unintended behavior. P1 Painful if we don't fix, won't block releasing

Comments

@diberry
Copy link
Contributor

diberry commented Feb 8, 2019

Sample information

  1. Sample type: web app bot, 4.x sdk, c#
  2. Sample language: dotnetcore
  3. Sample name: basic bot

Describe the bug

Issue #1 - Emulator 4 says it is connected but doesn't get past "couldn't send" regardless if I use development or production endpoint. Verified this also happens on Win10.

Issue #2 - Emulator 3 throws an error when running against local/development server. Verified this is a mac-only issue.

To Reproduce

In azure portal, created a new web app bot, SDK 4.x, c#, basic.
Downloaded zip file to local mac environment
Unzipped files
Opened solution with mac Visual Studio
Followed readme.md instructions in base of project (adding to appsettings.json file, and using emulator)

var adaptiveCard = File.ReadAllText(@".\Dialogs\Welcome\Resources\welcomeCard.json");

The full exception looks like the code isn't dealing with pathing correctly.

Expected behavior

Expect sample to work with both emulators and have the exact same behavior as the Portal's "Test in Web Chat" -- which works and shows the cards.

Screenshots

snip20190208_9
snip20190208_8
snip20190208_7
snip20190208_6

Additional context

Add any other context about the problem here.

[bug]

@sgellock
Copy link
Member

sgellock commented Feb 11, 2019

this has been fixed in the code generators. the Azure Portal needs an updated template with the fix. also the sample needs the fix too

@sgellock sgellock self-assigned this Feb 11, 2019
@sgellock sgellock added bug Indicates an unexpected problem or an unintended behavior. Approved P1 Painful if we don't fix, won't block releasing labels Feb 11, 2019
@diberry
Copy link
Contributor Author

diberry commented Feb 11, 2019

@sgellock Can you please give me ETA when it will show up in the Azure Portal ?

@sgellock
Copy link
Member

A couple of things will drive getting this fix into the portal. Currently we are close to releasing 4.3. I’ll update portal templates to use the 4.3 release. I don’t see this landing before early March. That said, a workaround would be to download the code from the portal, apply the fix referenced in the #1223 and az bot publish the local change back up to the portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or an unintended behavior. P1 Painful if we don't fix, won't block releasing
Projects
None yet
Development

No branches or pull requests

2 participants