Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Missing `directLine` prop?
See original GitHub issueScreenshots
Version
NPM: botframework-webchat ^4.13.0
Describe the bug
The directLine property is missing since version 4.13.0 in TypeScript
Steps to reproduce
- Run
npm install botframework-webchat - Follow one of the samples in this repo.
Expected behavior
directLine prop will be defined in Typescript.
Additional context
[Bug]
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
API reference - Direct Line API 3.0 - Bot Service | Microsoft Learn
Direct Line API 3.0 uses industry-standard REST and JSON over HTTPS. ... occurs because the Authorization header is missing or malformed.
Read more >Unity Direct Line interface returning [400] 'Missing Property ...
Unity Direct Line interface returning [400] 'Missing Property, Invalid or missing activities in http body' #4317.
Read more >MissingProperty error in Microsoft Bot Framework Request
I don't understand what property is missing though. Everything looks correct. javascript · node.js · azure · botframework · direct-line- ...
Read more >Direct Line Missed Payment - Here's What To Do 2022
Are you dealing with a Direct Line missed payment? If so, contact their support as soon as possible. If you don't, matters quickly...
Read more >Your HOME insurancE policy booklet - Direct Line
We will cover the buyer of your home under. Section 1 until the sale completes, as long as the property isn't insured under...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hrazmsft, yes. I was using ‘steps’ generally. I’ll respond here once I’ve run threw it.
@hrazmsft, I was able to repro the issue now. Turns out one of the culprits blocking me was yarn. Switching over to npm, I was able to encounter the errors you have reported. So, yes, I am now able to repro.
That being said, there is a comment further up that I missed that already identifies this as a known problem, issue #3856. Customers there report that downgrading to 4.11.0 alleviates the issue. It appears that 4.12.0 works for me. There will likely be a fix applied for 4.14 as the issue has been flagged for consideration.
As this appears to be a duplicate issue, I am going to close in favor of the other. If you are able, please add any comments there (if you haven’t already) showing support. Doing so will help in prioritizing development.