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.

Sign up for GitHub

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

Jump to bottom

Version 4.8 issues error "[onTurnError]: Error: missing activity.from.id" #2106

Closed
hinojosachapel opened this issue Mar 13, 2020 · 5 comments
Closed

Version 4.8 issues error "[onTurnError]: Error: missing activity.from.id" #2106

hinojosachapel opened this issue Mar 13, 2020 · 5 comments
Assignees
@tonyanziano
Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.

Comments

@hinojosachapel
Copy link

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.

Version

4.8.

Describe the bug

I was happily using version 4.7. Everything was fine. Then the "Update available" notification appeared and I proceeded with it. After that, I was unable to use the emulator. A consistent error was thrown from my bot: "[onTurnError]: Error: missing activity.from.id". After some time wasted figuring out what was happening, I uninstalled version 4.8 and reinstalled 4.7. And everything was right again. Now I continue to use 4.7 till this issue get fixed.

To Reproduce

Steps to reproduce the behavior:

  1. Just open a bot in the emulator version 4.8
  2. See error "[onTurnError]: Error: missing activity.from.id".

Expected behavior

To work as expected, just like in version 4.7.
[bug]
@hinojosachapel hinojosachapel added the Bug Your classic code defect label Mar 13, 2020
@tonyanziano tonyanziano added customer-reported Required for internal Azure reporting. Do not delete. Bot Services equired for internal Azure reporting. Do not delete. Do not change color. labels Mar 13, 2020
@tonyanziano
Copy link
Contributor

Hi @hinojosachapel ,

Thanks for reporting this issue. I'm sorry to hear that you're having trouble with the latest release.

Is there a certain scenario with your bot that causes this error to appear? Or are you just trying to send a message to your bot when you open it?

Is this happening at the stage of the conversation when it is first opened and the conversation update activity is sent, or is this later in the conversation when you try to send a message to the bot?

@tonyanziano
Copy link
Contributor

I have found the bug and am working on a fix.

@CezaryMarcjan CezaryMarcjan added the customer-replied-to Required for internal reporting. Do not delete. label Mar 16, 2020
@tonyanziano tonyanziano mentioned this issue Mar 16, 2020
Merged
@tonyanziano
Copy link
Contributor

tonyanziano commented Mar 16, 2020 •
edited
Loading

@hinojosachapel I have made a PR (#2108) that will fix the bug, and we aim to release a new patch (v4.8.1) of the Emulator later today or tomorrow that will include this fix.

@tonyanziano
Copy link
Contributor

tonyanziano commented Mar 17, 2020 •
edited
Loading

@hinojosachapel please update to the latest nightly version -- 4.8.0-113681 -- and try talking to a bot to verify that the issue has been fixed.

Please re-open the issue if not.

@hinojosachapel
Copy link
Author

@tonyanziano Thanks a lot. I can confirm that the issue has been fixed. Good work! Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tonyanziano tonyanziano

Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tonyanziano @hinojosachapel @CezaryMarcjan