Time to leave notifications

[MoparShaha]

I'm getting "Time to Leave" notifications for calendar events on my S4 Watch, even though Time to Leave notifications/settings are disabled on my iPhone. The events themselves don't have Time to Leave notifications set either. The notifications are sporadic. They only seem to randomly occur on iCloud calendars, not my Exchange calendars. The notifications only come through on the watch, not on the phone.

I've unpaired/repaired my watch multiple times, haven't had any luck. My next plan is to delete the offending iCloud calendar and reimport the events. Last idea is to erase the phone and setup as new, but I'd like to avoid that.

Has anyone else experienced this issue?

 

[waw74]

I have, it's been random enough that it doesn't bother me, so haven't looked into making it stop

my favorite is when i'm at work, and at 7:58 i get a "leave now to make it to work for 8:00"

 

[newtestleper]

Disable significant locations in your privacy settings.

 

[MoparShaha]

Disable significant locations in your privacy settings.

Thanks, I’ll give that a try!

 

[whsbuss]

Had a notification last night for dinner After dinner was over and was driving home.

 

[newtestleper]

Thanks, I’ll give that a try!

No charge!

 

[newtestleper]

Thanks, I’ll give that a try!

Success?

 

[MoparShaha]

Success?

Unfortunately, no. Just got another Time to Leave notification.

I tried toggling Time to Leave on and off again in the notification settings in Calendar. We’ll see if that fixes it.

 

[MoparShaha]

I tried toggling Time to Leave on and off again in the notification settings in Calendar. We’ll see if that fixes it.

That didn’t work. Seems to be a bug. Submitted feedback to Apple on the issue.

 

[skylarp]

Same problem here, S4 Apple Watch, iPhone X, up-to-date OSes. I experience it with both iCloud calendars and Google ones, and (perhaps most frustrating) it will use my work as a suggested location for these notifications even for events without explicit locations attached.

I went through some troubleshooting with @Applesupport on Twitter, but wasn’t able to resolve the problem. They suggested escalating to a phone support person, but I agree that it seems to be a bug and not a user error. Cross our fingers for watchOS 5.1.3 or 5.2, I guess?