Skip to content

Bugfix: schedule local notifications without a delegate - #555

Open
shiaho777 wants to merge 1 commit into
skiptools:mainfrom
shiaho777:fix-schedule-local-notifications
Open

shiaho777 wants to merge 1 commit into
skiptools:mainfrom
shiaho777:fix-schedule-local-notifications

Conversation

@shiaho777

Copy link
Copy Markdown

UNUserNotificationCenter.add returned without scheduling anything unless a delegate was set and willPresent included .banner or .alert. On iOS, add schedules the notification either way, and willPresent runs only when a notification fires while the app is in the foreground.

Scheduling no longer consults the delegate. NotificationWorker also used to call IconCompat.createWithResource with resource id 0 when the app had neither ic_notification nor ic_launcher, which failed the worker. It now falls back to android.R.drawable.stat_notify_chat.

add() returned without enqueueing work unless a delegate was set and willPresent included banner or alert. Scheduling no longer depends on that callback. NotificationWorker also uses a platform status icon when the app has neither a notification icon nor a launcher icon, instead of failing on resource id 0.
@cla-bot

cla-bot Bot commented Oct 9, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to the Skip community. We require contributors to sign our contributor license agreement (CLA), and we don't seem to have the user(s) @shiaho777 on file. In order for us to review and merge your code, for each noted user please add your GitHub username to Skip's .clabot file

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.

1 participant