Guest commenters return empty string

1

When retrieving the comment packets via the v4 api, it’ll return the user name of the commenter if they’ve been added to the project’s but if I send a share link to someone it returns a null entry for their username, even though on frameio I can see they have a name. Any ideas how to solve this?

2

@WikRik can you provide screenshots to show examples?

3

sure, here’s a video: Dropbox

you’ll see the comments in the web version by Ricky, when I get the data from the API it just crashes and returns nothing ‘LogPython: Error: :prohibited: Frame.io fetch error: ‘NoneType’ object has no attribute ‘get’‘ so I’ve changed the script to return ‘Unknown User’ if that field is empty. The question is, why does it return as empty? Is it because they’re not added to the project and it’s just from a share link? And if so, how come they’re down as ‘Ricky’ in the web version? I’d have thought the two would match. They do for people added to the project.

4

Thanks for the video, it’s helpful to see. I think this might be an issue with Anonymous users, aka someone who isn’t signed in nor directly a part of the project. I’ll log this as a bug.

5

glad it helps. Yes that seems to be what it is, although it’s odd that they still have a username in frameio directly, hopefully can be resolved.

6

Piling on here. I’m having the same issue. In v3, my automation would return the person’s name, even if they weren’t invited to a project. This was handy as we have an automation that pulls comments into a slack channel, and we could see who was commenting without needing to open the frame link. In v4, it doesn’t return any data for these same people, it only returns names for registered users on our Frame team.

7

I’m finding v4 does return them sometimes, but other times / users not

8

Hi @spencerframe this is working by design, as with privacy concerns we do not keep the user data that is not associated with the Frame account. I’ve flagged this again to see if we can surface an alternative way but this was a change from how we did it in v3 to v4 due to the privacy concerns from some customers.