Skip to content

RSS to AP bot error - (Protocol.UndefinedError) protocol Enumerable not implemented for nil

I followed a RSS to AP bot but don't seem to be receiving messages from it. I started watching the logs and started noticing the error below. This is only happening for the bot that I'm following as far as I know so this might be an issue with the bot and not Pleroma.

09:54:55.937 request_id=2m6h43cds6c77qkhsfs0lap1 [info] POST /users/tiker/inbox
09:54:55.954 request_id=2m6h43cds6c77qkhsfs0lap1 [info] Fetching object https://bots.tinysubversions.com/u/Raspberry_Pi_Blog_News via AP
09:54:56.555 request_id=2m6h43cds6c77qkhsfs0lap1 [info] Sent 200 in 617ms
09:54:56.556 [info] Handling incoming AP activity
09:54:56.581 [error] Task #PID<0.3735.4> started from Pleroma.Jobs terminating
** (Protocol.UndefinedError) protocol Enumerable not implemented for nil. This protocol is implemented for: DBConnection.PrepareStream, DBConnection.Stream, Date.Range, Ecto.Adapters.SQL.Stream, File.Stream, Floki.HTMLTree, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, List, Map, MapSet, Postgrex.Stream, Range, Stream, Timex.Interval
    (elixir) lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir) lib/enum.ex:141: Enumerable.reduce/3
    (elixir) lib/enum.ex:2979: Enum.uniq_by/2
    (pleroma) lib/pleroma/web/activity_pub/utils.ex:612: Pleroma.Web.ActivityPub.Utils.make_create_data/2
    (pleroma) lib/pleroma/web/activity_pub/activity_pub.ex:168: Pleroma.Web.ActivityPub.ActivityPub.create/1
    (pleroma) lib/pleroma/web/federator/federator.ex:141: Pleroma.Web.Federator.perform/2
    (elixir) lib/task/supervised.ex:89: Task.Supervised.do_apply/2
    (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
Function: #Function<1.27536759/0 in Pleroma.Jobs.maybe_start_job/4>
    Args: []

I am (or was) running on the development branch but this has been an issue for a few months now. I tried updating from development branch but it seems the latest LDAP related changes prevent the development branch from running so I don't know if this has been recently fixed.

Thanks.