persist callback URL across various navigations.

[Abu-bkr]

Description

When navigating to the sign-in or sign-up page in the app, the URL does not persistently retain the callback parameter. As a result, after successful authentication, users are not redirected to the specified callback destination or the desktop app. This behavior limits the user flow and fails to direct users back to their intended page after authentication, which is essential for maintaining a smooth and consistent experience.

Steps to Reproduce

Navigate to the sign-in or sign-up page with a callback parameter in the URL (e.g., https://trypear.ai/signin?callback=app://dashboard).
Complete the authentication process (log in or sign up).
Observe the redirection behavior post-authentication.

Expected Behavior

After successful authentication, users should be redirected to the specified callback URL, ensuring they return to the intended page or app flow without needing to navigate manually.

Actual Behavior

After authentication, the callback URL parameter is lost, and users are redirected to the default page instead of the specified callback destination. This breaks the intended user flow and requires users to manually navigate back to their desired page.

Additional Information

This issue affects user navigation and breaks the user experience in workflows where a custom callback is required for redirection post-login or sign-up. Proper handling of the callback parameter allows users to seamlessly return to the desktop app or specific URLs after signing in.

[Abu-bkr]

hello , I am tackling this issue, ok can you assign it to me