BGContinuedProcessingTask Notification Error

Question

Created 2d

Replies 1

Boosts 0

Participants 2

Hello im creating an expo module using this new API, but the problem i found currently testing this functionality is that when the task fails, the notification error doesn't go away and is always showing the failed task notification even if i start a new task and complete that one.

I want to implement this module into the production app but i feel like having always the notification error might confuse our users or find it a bit bothersome.

Is there a way for the users to remove this notification?

Best regards!

Boost

Answer 1

DTS Engineer OP

Apple

1d

Hello, I’m creating an expo module using this new API, but the problem I found currently testing this functionality is that when the task fails, the notification error doesn't go away and is always showing the failed task notification even if I start a new task and complete that one.

By "failed", do you mean passing "false" to "setTaskCompleted(success:)"?

I think one of the critical things to understand about this API is that you need to think of it as more of an "interface" API, and less a "work scheduling" API. In the case here, the exclamation point is there and the UI is staying put because you said the work was not done (by passing "false") and we're passing that information to the user (by not dismissing the UI). If that doesn't really "fit" your particular work and you just want the UI to dismiss, then you can pass "true" to and the UI will dismiss immediately.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0