Hello, I found this forum thread aligns with what I am finding in one of my apps. Although I don't have a standalone watch app, the conditions described here are what my app is experiencing. My watch ext can independently connect to internet via wifi or cellular connection only when disconnected from phone (operating independently). If watch is connected to phone via BLE but the phone is disconnected from network (no wifi or cellular data) URLSession tasks on watch fail with Code=-1009 as described in post. Why can't the watch use its local wifi connection instead of relying on connected phone? Is network permission required in this case? I thought local network permission was only for discovery and connecting devices on local network while internet connectivity can still operate without this permission. Does granting this permission workaround the issue of watch using local network connection rather than relying on connected phone? Is there a setting I'm missing to tell watch ext to use local network connection first before trying on phone? Any advice is appreciated. -Brian.

Hi gorka-mk, I might be able to help if I can get my 3rd party accessory up and running with background mode. I understand that is not the issue you describe here but maybe once I get it working can look into the direction nil issue as I also need this to work. Can you provide any detail on how you got your 3rd party accessory working with Nearby Interaction Service (BLE GATT service) required to support background mode? I am currently working with Qorvo DWM3001CDKE development board. Stuck on BLE advertising both the UART and Nearby Interaction Service. I'd appreciate any direction on how you got this working. Thanks, -Brian.

Same issue. Since watchOS 8 I have not been able to fire local notifications without a long delay even when setting the trigger to nil or some brief time interval like 0.1 to 1 second. Local notifications with timely delivery are critical to app functionality. I hope Apple can address this issue soon or provide a workaround. I'll post a solution if I find one.

I had the same issue since updating to Xcode 12.5. However, what I discovered is opened Swift packages loop on resolving if you use a relative location for DerivedData. Try opening Xcode 12.5 preferences go to Locations and set DerivedData to default location. Problem went away for me. This is a less destructive way to solve this problem rather than deleting Xcode configuration.

Update. Turns out it was null values in custom payload. Replacing null values with empty strings "" worked for us.

Can confirm same issue with no great workaround. I started eliminating extra payload key/values and got it to work after removing ones with ISO8601 date strings and empty strings (not null just empty ""). This discovery is still work in progress so I can't say for certain if it was the date or empty strings. If you have the ability to easily remove/change k/v in your custom payload, I'd suggest doing so to eliminate the offending values. This may not offer a solid workaround since your app could depend on accuracy of those values.