I came across a scenario where a user had an old cookie (thirdparty) and i swapped the recipe over to thirdpartyemailpassword... So I think it was looking for thirdparty.Init.. any suggestions on how to not bork all users who have logged in via thirdparty recipe

Hey @Erick you should switch to thirdpartyemailpassword on the frontend and backend. And it should work without any issues.

interesting..

When you say that it was looking for thirdparty.init, what do you mean?

I think you may be importing from thirdparty somewhere and using one of its functions

I removed references to thirdparty entirely on frontend/backend. This was a user report on dev branch. Would the

rid

request header have anything to do with it? Also possible they were just running a cached version and needed to do a hard refresh

rid header wouldn’t cause this issue

hm i found one reference to it

Yea. The error stack has the function name

Fixed TY @rp_st !