Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PP-11638 Move client-side logging for wallet available #3755

Closed

Conversation

stephencdaly
Copy link
Contributor

We were logging that wallet payment methods were shown to the end user fewer times than they were being selected.

Move where we log whether the the wallet methods are available to the same place we add the classes to make the buttons visible. What was probably happening was a race condition between the JavaScript that shows the button and the JavaScript that checks whether the button is shown to log the message.

Remove the code that just sends some Google Analytics events as we do not use Google Analytics currently, and have not for some time.

Additionally, log when we remove the Wallet buttons because our scripts haven't loaded properly.

We were logging that wallet payment methods were shown to the end user
fewer times than they were being selected.

Move where we log whether the the wallet methods are available to the
same place we add the classes to make the buttons visible. What was
probably happening was a race condition between the JavaScript that
shows the button and the JavaScript that checks whether the button is
shown to log the message.

Remove the code that just sends some Google Analytics events as we
do not use Google Analytics currently, and have not for some time.

Additionally, log when we remove the Wallet buttons because our
scripts haven't loaded properly.
@iqbalgds
Copy link
Contributor

iqbalgds commented Nov 6, 2023

Looks good - some Cypress test's are failing

@stephencdaly
Copy link
Contributor Author

Looks good - some Cypress test's are failing

Thanks - I think what I tried isn't going to work. Will have to try something else

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants