Here’s what happens step-by-step:
When a non-logged-in user opens a deep link (e.g. /job?recordId=rechjD5lpGXPNoTc0) → they get redirected to the sign up flow with ?next-page=/job?recordId%3DrechjD5lpGXPNoTc0 attached.
This is working fine.
When they finish the sign up flow, they get automatically redirected to the Onboarding Flow. There, the URL parameters look like this: /onboarding?recordId=rechjD5lpGXPNoTc0&next-page=/job
After the Onboarding Flow they are redirected to /job and the recordId is lost.
Is anyone else running into this issue? Am I missing something?
It does seem odd that the feature exists for deep linking (with the /next-page solution) but it doesn’t work with a record attached to it. I imagine this is an important requirement.
For us, it’s quite a big issue that we cannot deeplink to any records. I’d appreciate any updates or if there’s any workarounds I could try!
I spoke to the team about this, and it’s actually something that we want to do and are planning on supporting. They were checking in with the code and trying to figure out how to make it happen. Once I learn more, I’ll let you know, but the hope is to get it live soon.
In the meantime, I’ve coded a workaround that strips the URL parameters and saves them into localstorage to then restore after onboarding. But a native way would be much saver
