This error was related to a cross promotion feature that we were working on, an update is coming and this will be fixed if still persists :)
