I am not 100% sure exactly what I did to make this happen but here are some of the steps I took. Sorry, I cannot remember the exact order in which I performed them.
I signed out of iCloud on both the Mac and the iPhone I removed my Apple ID from the family sharing that I was a part of I signed back into iCloud on both devices I had my wife invite me back into the family sharing group I followed somebody’s advice that said to close the calendar event after I had created it. To do this is not so obvious. For example, here’s what I did: Command N to create a new event Name the event and add the date and time followed by Enter Adjust the details and VO right arrow to the show button and VO space Bar At this point, the calendar event disappears and you are back on the calendar However, you still need to press command accent to switch windows within the application to find the calendar event dialogue Now press command W to actually close the event dialogue Now I can create new events on the Mac calendar and they appear on the Mac, the iPhone, iCloud, and Google calendar online. It worked for both my “home” iCloud calendar and the family shared calendar. I haven’t gotten around to trying to see how important it is to actually close the calendar event dialogue as described above. Hopefully this helps out somebody else in the future. On Tuesday, March 15, 2016 at 12:41:39 AM UTC-7, Sabahattin Gucukoglu wrote: > > I had this problem, too, until I learned to press the close button in the > calendar appointment. > > Until you do that, the change is not submitted to the server. Yes, even > if it shows up in the flaming list as booked. Even if you quit and restart > Calendar, and it continues to show. > > Here’s something you should know: the client is responsible for > interpreting the iCalendar document. The file is picked up from the server > and interpreted locally. So anything you see locally is law. Doesn’t > matter what some other client says. Relying on some other client to > provide an accurate description when you intend the event to be interpreted > on a different client is thus not a good idea. Trust, but verify. :) -- The following information is important for all members of the Mac Visionaries list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your Mac Visionaries list moderator is Mark Taylor and your owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/macvisionaries@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at https://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
