OG requires a visibility field on the group itself (i.e. not only on the group-content).

Below problem solved in commons 7.x-3.3-rc4
******************************************
trying to add a post to the group I get following excetpion:
OgException: Cannot set visibility of node ID 13 as the group node of type "user" does not have the "Group visibility" field attached to it. in _og_access_verify_access_field_existence() (line 250 of /srv/www/htdocs/commons7x33rc2/profiles/commons/modules/contrib/og/og_access/og_access.module).

The same happens with a Public group with "Any site member can contribute"

I have exactly the same problem.

How did you solve it?

I triggers when rebuilding permissions and when I try to create a node with "use group defaults" as visibility.

Now I've solved my problem. Apparently I had accidently selected "Posts" to be groups and group content despite being supposed to only be content posted to a group.

The error message I got was:
OgException: Cannot set visibility of node ID 326 as the group node of type "post" does not have the "Group visibility" field attached to it. in _og_access_verify_access_field_existence() (line 250 of /var/www/***/sites/all/modules/og/og_access/og_access.module).

Apparently this became an issue because the
_og_access_verify_access_field_existence($node) {

Didn't exist in older versions of OG Access and now it seem to test all content types each time you post any node.

I am not sure on if this is intended but that is how it works.

For this error:

OgException: Cannot set visibility of node ID 54 as the group of type "open_group" does not have the "Group visibility" field attached to it. in _og_access_verify_access_field_existence() (line 250 of D:\xampp\htdocs\p\sites\all\modules\og\og_access\og_access.module).

See #2063385: _og_access_verify_access_field_existence() assumes node group type, throws an exception rebuilding node access.

Can you explain how to add group visibility field to the group? My group members have lost their ability to see each others' user profiles or any access to their fellow group members.

Try this.

1. Go to Administration » Configuration » Organic groups » OG field settings,
2. In the Bundle dropdown select your group,
3. In the Fields dropdown select 'Group visibility',
4. Click Add field

That fixed it for me.

Thank you.

I encountered the same error after upgrading and trying to rebuild permissions. The og-access, field visibility issue created access problems in the first place which is why I tried to rebuild them.

I tried to add the visibility field to my groups via #8; however, I got an error saying that the visibility field could only by added to Node Entities, which my group is. It is noteworthy to add that I updated the OG module and the Entity module at the same time, because they both had security updates.

My final solution was to revert back to the previous version of OG and rebuild the permissions. Things are now working as expected, but it doesn't fix/explain the issue in the upgrade other than that the problem lies with the visibility field in the og access module.

#8seems to be the right answer - OG now forces you to have a visibility field on the group itself (i.e. not only on the group-content).

After updating to og 7.x-2.3 I have the same error when trying to rebuild permissions or update group content which have a relation with different group types - node and user groups for my case:
"OgException: Cannot set visibility of node ID 812 as the group node of type "user" does not have the "Group visibility" field attached to it. in _og_access_verify_access_field_existence() (line 250 of sites/all/modules/og/og_access/og_access.module)."
So as an OG field access ('Group visibility') can be added only to the node group then I guess need to verify in the _og_access_verify_access_field_existence() function only the node groups

Re-roll for 7.x-2.4

Change the version

14: 2063479-error-on-rebuilding-permissions-14.patch queued for re-testing.

#8 Also worked for me... Years later.