I'm not sure I understand; that's the way it's supposed to work? See the docs for init(dateMatching:repeats:): Discussion If you specify true for the repeats parameter, you must explicitly remove the notification request to stop the delivery of the associated notification. Use the methods of UNUserNotificationCenter to remove notification requests that are no longer needed. So in response to, say, some user action you have to remove the notification yourself.

I think I was able to solve a similar problem, though my problem was slightly different. The short answer is: use at least a .userInitiated qualityOfService in Catalyst; when the qualityOfService is .default (or below) requests become discretionary when the app is in the background (i.e., inactive). And I think that's where the problem is. For a longer answer, see my response on Stack Overflow.