uhooi/UhooiPicBook

non-sendable type warning occurs

uhooi opened this issue · 1 comments

uhooi commented

Warnings

Logs

.../UhooiPicBook/App/UhooiPicBookWidgetsConfigurableIntent/IntentHandler.swift:27:42: cannot use parameter 'self' with a non-sendable type 'IntentHandler' from concurrently-executed code
.../UhooiPicBook/App/UhooiPicBookWidgetsConfigurableIntent/IntentHandler.swift:31:17: cannot use parameter 'completion' with a non-sendable type '(INObjectCollection<MonsterIntentObject>?, Error?) -> Void' from concurrently-executed code
.../UhooiPicBook/App/UhooiPicBookWidgetsConfigurableIntent/IntentHandler.swift:33:17: cannot use parameter 'completion' with a non-sendable type '(INObjectCollection<MonsterIntentObject>?, Error?) -> Void' from concurrently-executed code
.../UhooiPicBook/App/UhooiPicBookWidgets/Monster/MonsterConfigurableWidget.swift:51:36: cannot use parameter 'self' with a non-sendable type 'MonsterProvider' from concurrently-executed code
.../UhooiPicBook/App/UhooiPicBookWidgets/Monster/MonsterConfigurableWidget.swift:51:59: cannot use parameter 'intent' with a non-sendable type 'MonsterProvider.Intent' (aka 'SelectMonsterIntent') from concurrently-executed code
.../UhooiPicBook/App/UhooiPicBookWidgets/Monster/MonsterConfigurableWidget.swift:53:13: cannot use parameter 'completion' with a non-sendable type '(Timeline<MonsterProvider.Entry>) -> Void' (aka '(Timeline<MonsterEntry>) -> ()') from concurrently-executed code

Screenshot

Warnings
スクリーンショット 2022-01-11 13 12 58

👋 Thanks for reporting!
Please PR :)