Chat fails to send with error "no TLF name specified"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I tried sending a message to a group message and was presented with the error below.
Keybase GUI Version: 1.0.18-20170223162556+af0e640
Error: no TLF name specified at t (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:17:24269) at new t (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:17:25090) at s (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:17:24665) at i (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:17:24593) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:12:22245 at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:81:27307 at e.t.Deferrals.e._call (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:42:29301) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:42:29452 at c (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:42:29079) at e.t.Deferrals.e._fulfill (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:42:29411)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure when sending a group message in Keybase GUI version 1.0.18. Inspect the reported entry point in desktop/dist/index.bundle.js and trace the “no TLF name specified” error; done means a group message sends successfully without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100