[GH-ISSUE #28] Double event callbacks using on(event, callback) syntax #25

New issue

Closed

opened 2026-05-23 08:26:25 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:26:25 -06:00

Owner

Originally created by @appy-one on GitHub (Apr 1, 2021).
Original GitHub issue: https://github.com/appy-one/acebase/issues/28

Originally assigned to: @appy-one on GitHub.

Events 'value', 'child_added' and 'notify_child_added' are fired twice for each value when using ref.on(event, callback) syntax.
To reproduce:

db.ref('messages').on('value', snap => {
   console.log('value callback'); // Prints twice
});

db.ref('messages').on('child_added', snap => {
   console.log('child_added callback'); // Prints twice for each child
});

db.ref('messages').on('notify_child_added', ref => {
   console.log('notify_child_added callback'); // Prints twice for each child
});

This does not happen when using ref.on(event).subscribe(callback)

Originally created by @appy-one on GitHub (Apr 1, 2021). Original GitHub issue: https://github.com/appy-one/acebase/issues/28 Originally assigned to: @appy-one on GitHub. Events 'value', 'child_added' and 'notify_child_added' are fired twice for each value when using `ref.on(event, callback)` syntax. To reproduce: ```js db.ref('messages').on('value', snap => { console.log('value callback'); // Prints twice }); db.ref('messages').on('child_added', snap => { console.log('child_added callback'); // Prints twice for each child }); db.ref('messages').on('notify_child_added', ref => { console.log('notify_child_added callback'); // Prints twice for each child }); ``` This does not happen when using `ref.on(event).subscribe(callback)`

gitea-mirror added the

bug

label 2026-05-23 08:26:25 -06:00

gitea-mirror referenced this issue

2026-05-23 08:26:26 -06:00

[GH-ISSUE #25] Docs for proxy.onMutation((mutationSnapshot, isRemoteChange) and possible issue. #26

gitea-mirror closed this issue

2026-05-23 08:26:27 -06:00

gitea-mirror commented

2026-05-23 08:26:29 -06:00

Author

Owner

@appy-one commented on GitHub (Apr 2, 2021):

Fix published in acebase-core v1.4.1, which is now required by acebase v1.5.0 and acebase-client 1.3.2

@appy-one commented on GitHub (Apr 2, 2021): Fix published in acebase-core v1.4.1, which is now required by acebase v1.5.0 and acebase-client 1.3.2