lucas_van_dongen
This is my and my organization’s first Elixir / Phoenix project so far. I have been able to set up a working prototype and got the green light to turn it into a full product. The only thing so far I haven’t been able to solve myself is the fact that the (iOS, Android and Web) clients send heartbeat but Phoenix doesn’t seem to do anything with it.
[warn] Ignoring unmatched topic "heartbeat" in MyApplication.UserSocket
Most documents that mention heartbeat mention it like a feature that’s just there. Also there’s some code in transport.ex that seems to take care of it. However I’m getting that warning and the clients drop after around 60 seconds.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
outlog
what client code/libraries are you using?
from that error it seems like your client is trying to connect to a “heartbeat” channel, which isn’t quite normal.. (afaik - the heartbeat goes in a “phoenix” channel - but your client lib should handle it all..)
lucas_van_dongen
For Swift I’m using
SwiftPhoenixClient. Seeing this in my output:socket received: {"topic":"heartbeat","ref":"3B151654-07A0-4BED-9C09-27F5881B6118","payload":{"status":"error","response":{"reason":"unmatched topic"}},"join_ref":null,"event":"phx_reply"} Phoenix Response: ref:"3B151654-07A0-4BED-9C09-27F5881B6118", event:"phx_reply", topic:"heartbeat", payload:["status": error, "response": { reason = "unmatched topic"; }]idi527
There’s also GitHub - sjrmanning/Birdsong: 🐦🎼 Swift WebSockets client for Phoenix Channels. · GitHub for swift which doesn’t have this particular error …
outlog
is it also the js client? or only the swift one? (that breaks)
lucas_van_dongen
I just compared to be sure. But Birdsong isn’t super actively updated while SwiftPhoenixClient is. I’m trying to update SwiftPhoenixClient now, it was a while since I updated it.
idi527
There isn’t much to a phoenix channel client.
phoenix.jsisn’t often updated either … As for the SwiftPhoenixClient, it was abandoned before someone else picked it up and started rewriting it.lucas_van_dongen
I notice. There’s a ton of API changed. Have to rewrite my code and try again.
lucas_van_dongen
OK guys we can wrap it. A newer version works great. So it was sending the wrong message all of the time.
@idi527 thanks for the hint, luckily the library is maintained.