Extra Parameters in Call Update
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.4k
- Forks
- 472
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Issue Summary
Extra parameters are being sent along in my Call Updates — in particular, StatusCallbackMethod, Method, and FallbackMethod are all being sent to Twilio with the values of "POST" even though I didn't specify them in my actual calls(id).update( ... ) call.
This wouldn't be a big deal except that I think by specifying the method for any of these endpoints, the actual URL stored for them gets reset. So my incoming calls, which had a Status Callback URL set by the TwiML App assigned to that phone number, were having their Status Callback URLs reset any time I used the Call Update API.
Steps to Reproduce
- Start a call
- Update it from the Ruby client
Code Snippet
# Example for ending a call from the server
Twilio::REST::Client.new.calls(twilio_call_sid).update(
status: :completed
)
Exception/Log
Completed parameter was sent but so were the other parameters.
Technical details:
- twilio-ruby version: 6.7.1
- ruby version: 3.2.2
(Twilio Ticket 15197987)
Contributor guide
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 at the Ruby client's calls(...).update entry point and inspect how update parameters are assembled. Reproduce the request with status: :completed, then verify that only explicitly supplied parameters are sent and existing callback URLs are not reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100