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

Concurrency issue in BlazeLocalNotificationScheduler #14011

Closed
Tracked by #14050
itsmeichigo opened this issue Sep 23, 2024 · 1 comment · Fixed by #14012
Closed
Tracked by #14050

Concurrency issue in BlazeLocalNotificationScheduler #14011

itsmeichigo opened this issue Sep 23, 2024 · 1 comment · Fixed by #14012
Assignees
Labels
feature: Blaze Related to the integration of the Blaze ads platform type: bug A confirmed bug.

Comments

@itsmeichigo
Copy link
Contributor

Describe the bug
When enabling Core Data concurrency debug, I encountered an error in DefaultBlazeLocalNotificationScheduler.scheduleNoCampaignReminder.

Screenshots
image

Expected behavior
There should be no concurrency issue with DefaultBlazeLocalNotificationScheduler.

@itsmeichigo itsmeichigo added type: bug A confirmed bug. feature: Blaze Related to the integration of the Blaze ads platform labels Sep 23, 2024
@dangermattic
Copy link
Collaborator

Thanks for reporting! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Blaze Related to the integration of the Blaze ads platform type: bug A confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants