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

Event listener doesn't fire when creating associated accounts #356

Open
armaniferrante opened this issue Jun 2, 2021 · 2 comments
Open
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed ts

Comments

@armaniferrante
Copy link
Member

armaniferrante commented Jun 2, 2021

It's been reported that initializing an associated account in the same transaction of emitting an event causes the event listener not to be fired on the client. Repro case here https://gist.github.com/0xkarl/f9f40e9d057f7e4497c338cbedd5e7ae.

The logs indeed have the event so it's expected that this is a bug in the log parsing logic here https://github.com/project-serum/anchor/blob/master/ts/src/program/event.ts#L13.

@Standaa
Copy link
Contributor

Standaa commented Jun 15, 2021

Can confirm this behaviour.
Event fires in program, but the client-side event listener never is. I am initializing an associated account in the same Tx as well.

@armaniferrante armaniferrante added good first issue Good for newcomers help wanted Extra attention is needed labels Jun 15, 2021
@Standaa
Copy link
Contributor

Standaa commented Jun 16, 2021

Started addressing it here: #397

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed ts
Projects
None yet
Development

No branches or pull requests

2 participants