You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many websites will perform an HTTP redirect or Js side location update when hitting e.g. the root page. To handle the enabling of the toolbar, we are passing a url hash, via a redirect from app.posthog.com, which we then look for in the posthog-js init code. If there is a redirect before this init code has a chance to run, then we do not see the toolbar launch.
This could be handled on the website side, ensuring that the init code is run before redirect, or the hash is maintained across redirect but this would complicate the app side and ideally we shouldn't expect people to have to change their app to use the toolbar.
How to reproduce
setup or use a page that redirects/changes the url before posthog-js init method runs
use this page as the launch url
Click launch in the app.posthog.com ui
Environment
PostHog Cloud
self-hosted PostHog, version/commit: please provide
The text was updated successfully, but these errors were encountered:
Bug description
Many websites will perform an HTTP redirect or Js side location update when hitting e.g. the root page. To handle the enabling of the toolbar, we are passing a url hash, via a redirect from app.posthog.com, which we then look for in the posthog-js init code. If there is a redirect before this init code has a chance to run, then we do not see the toolbar launch.
This could be handled on the website side, ensuring that the init code is run before redirect, or the hash is maintained across redirect but this would complicate the app side and ideally we shouldn't expect people to have to change their app to use the toolbar.
How to reproduce
Environment
The text was updated successfully, but these errors were encountered: