Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Shared Photo Album Link Doesn't Work.

A friend of mine has shared an album with me. I have a received an email saying that the album has been shared. There's a link in the email to click.


The problem is that nothing happens (other than Photos opening up) when I click the link. The album isn't shared.


The odd thing is that this same person has shared an album (a different album) with me in the past (two weeks ago) - and I still see this shared album. However, for whatever reason she can't share an additional photo album with me.


So I asked my friend to resend the invite. She did. Same thing. Link opens my Photos - but the album she intends to share isn't there. She has updated her iPhone recently. Maybe the update broke everything. My system is 100% the same as before (no updates on my end either).


Why?


I feel like I'm using a Microsoft Windows operating system - where nothing works and no one knows why.


Anyway - is the Apple Photo sharing mechanism so fickle that you MUST use a CERTAIN email address (such as my address associated with my account). I wouldn't think that'd be necessary since one could always log into your iCloud account (or whatever account you'd call it).


Well, we can always share photos using Google Drive.



1 reply

I believe I found the problem. At least for my setup - I cannot accept an invite to a shared photo album using my MacBook Pro. However, I can accept an invite link using my iPhone.


I have Photos connected to both to my iPhone and my MacBook Pro. When using my MacBook Pro clicking the link opens Photos - but, no album is shared. However, if I click that same link using my iPhone it works - the album is shared.


Again, both my MacBook and iPhone share the same photos in Photos. Whatever albums and pictures I see on my iPhone will also be viewable (and editable) on my MacBook Pro.


So, I guess something is dysfunctional - but, at least I found the workaround.