iCloud and strange iCal behavior if you receive external calendar requests?

Discussion in 'Apple Music, Apple Pay, iCloud, Apple Services' started by omega1848, Dec 12, 2011.

  1. omega1848, Dec 12, 2011
    Last edited: Dec 12, 2011

    omega1848 macrumors newbie

    Joined:
    Dec 12, 2011
    #1
    Hi there,
    I have the following problem and asking myself how useful iCloud in reality is...
    Background: I have installed and set up iCloud on my MacBook Pro and on my iPhone, I am using my Apple ID for iCloud, which is firstname@lastname.com, so in other words not an MobileMe email address (since Apple recommended to use the Apple ID to sign in to iCloud).

    Now I have enabled calendar sync within iCloud and if I set up a calendar entry on my iPhone, it appears and syncs shortly after on my MBP and vice versa, and I have no local calendars on my MBP or iPhone.

    If I am sending out an invite within iCal to someone else, then the invite is being send with my correct email address firstname@lastname.com, exactly as I expected and hoped (because I do not want to have the situation like it was in the past with MobileMe, that always the MobileMe email address was being used for calendar requests or replies, which confused my customers and friends, because the never knew which address to use to send me an email or invite).

    The editing, deleting of the calendar entry works without a problem in that scenario.
    So far, so good...

    But now my problem:
    If someone else from external is sending me a calendar request/ invite to my firstname@lastname.com email address, I see the .ICS attachment within the email and I can click on it to have it accepted to my iCal on my iPhone. But if I check the calendar on my MBP or via the web access of iCloud, the calendar entry shows up as "not being accepted yet", so "grayed out".
    But I am sure have accepted it on the device, in addition to that I am not able to delete or edit the calendar entry on my device, there is no "edit" button anymore for this entry! Not even delete is possible? Why that?

    This is even more annoying if I receive an update for this invite (for example time or location has changed, etc.), I am not able to either update the entry, or at least to delete it first and then accept the new invite...

    What is going on there? Why is that not working?
    Does this really only work with MobileMe name@me.com email address / iCloud identifier?
    If that is the case, then I must admit that iCloud is still useless for me...
    Because then the calendar requests and replies are done via name@me.com address, which is causing confusion on the other end (partners, customers, friends...)

    Any ideas, anyone who has this working with a Apple ID which is not (!) a name@me (MobileMe) email address?
    Thanks in advance for your help!
     
  2. thomahawk0 macrumors member

    Joined:
    Jul 9, 2008
    #2
    Similar Issues

    I have the same issue happening (see my other thread: http://forums.macrumors.com/showthread.php?t=1291983) and it's quite annoying. I'm missing appointments that are scheduled and sent to me an hour or two before I need to attend and don't have time to go through the 30 emails i received between meetings to ensure I didn't miss an invite. Worst part, it was working like a champ up until Wednesday afternoon/evening. :mad:
     
  3. rcha101 macrumors member

    Joined:
    Feb 28, 2006
    #3
    I also have the same problem.

    I notice also that when you receive an invite via email:
    -clicking on the .ics attachment does nothing
    -click Accept in the email invite opens a web page, if I open the ICS link from there I can open it in calendar and choose the calendar it goes into. This works fine.

    What I would like is for the invites to show up on Calendar (mac and phone) as a badge and have the ability to accept from there. As it potentially depends on which address the invite is sent to (not from) this is problematic as people may continue to use my old gmail address. It used to work I just don't know why Apple had to change the behaviour.
     

Share This Page