akramic

akramic

I’m trying to follow the documentation on using Elixir as a Presence Client as outlined here: [Phoenix.Presence — Phoenix v1.8.8]

Channel join code :

@impl true
  def join("online", params, socket) do
    IO.inspect(params, label: "PARAMS on join")
    send(self(), :after_join)
    {:ok, socket}
  end
  @impl true
  def handle_info(:after_join, socket) do

    IO.inspect(socket)
    user_id = socket.assigns.user
    {:ok, _} = Presence.track(socket, user_id, %{
      user_id: user_id,
      online_at: inspect(System.system_time(:second))
    })
    push(socket, "presence_state", Presence.list(socket))
    {:noreply, socket}
  end



Code for presence.ex



    def init(_opts) do
      {:ok, %{}} # user-land state
    end

    def handle_metas(topic, %{joins: joins, leaves: leaves}, presences, state) do

      IO.inspect(joins, label: "JOINS")
      # fetch existing presence information for the joined users and broadcast the
      # event to all subscribers
      for {user_id, presence} <- joins do
        user_data = %{user: presence.user, metas: Map.fetch!(presences, user_id)}
        msg = {MyApp.PresenceClient, {:join, user_data}}
        Phoenix.PubSub.local_broadcast(MyApp.PubSub, topic, msg)
      end

      # fetch existing presence information for the left users and broadcast the
      # event to all subscribers
      for {user_id, presence} <- leaves do
        IO.inspect(joins, label: "LEAVES")
        metas =
          case Map.fetch(presences, user_id) do
            {:ok, presence_metas} -> presence_metas
            :error -> []
          end

        user_data = %{user: presence.user, metas: metas}
        msg = {MyApp.PresenceClient, {:leave, user_data}}
        Phoenix.PubSub.local_broadcast(MyApp.PubSub, topic, msg)
      end

      {:ok, state}
    end
end

I’m able to join the channel but get the following error:

(KeyError) key :user not found in: %{metas: [%{user: 1, online_at: "1728611576", phx_ref: "F_1DEghkHFXOsARm"}]}

I think that the error is due to this line:

user_data = %{user: presence.user, metas: Map.fetch!(presences, user_id)}

I’d be grateful if someone could point me in the direction of resolving this error.

Many thanks and apologies if this duplicates another post - I couldn’t find anything related to this on the forum.

Showing Posts 1 to 1

akramic

akramic OP

This is called because this line
`

`
should be

 user_data = %{user: user_id, metas: Map.fetch!(presences, user_id)}

and

  user_data = %{user: presence.user, metas: metas}

should be

user_data = %{user: user_id, metas: metas}

I wasn’t looking closely enough at the data structure for presences and presence.

Hope it helps someone.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews