Villagers will not breed

Thanks I thought I did something wrong. Good to know for future reference that the resolved status was just policy.

Were these villagers cured from zombie villagers prior to the 1.16 update? No
Do they have workstations? Yes
Are there any other villages nearby? No, it is on a small island in the middle of an ocean
Are they linking to the beds, and sleeping in them? Yes

Finally, would you be able to provide a copy of the world save? No, I do not have access to this. Not my realm. I will see if I can get the world from the owner though.

Since it’s a realm, see if the owner can close and reopen the realm. That was the workaround for MCPE-49580, which is supposed to be fixed in 1.16. It could be some residual part of that bug.

Also, btw tickets resolved to “awaiting response” automatically reopen when the owner comments.

Hello, I am the owner of the realm.... I tried closing and opening it this morning.  I also just tried to upload the world to this ticket, but it is too big... 1.1GB....I get a message saying the max file size is 10MB.

Is everyone in the realm having the same problem?

No one else has tried yet, but I have tried with 2 different villages. 

Here is a link to the world files:

https://drive.google.com/file/d/1pTy_OdAmsRR8dZ5t2ZlM_R3RvoLw7aJD/view?usp=sharing

Quick update, other users on our realm can't get villagers to breed either.

FYI: breeding works fine, when loading the world locally. 

Make sure there are no other villagers within 100 blocks. Give the villagers bread to start the breeding. Once they start no further giving is needed.

The village is very far from other villages well over 100 blocks. The villagers now have more than a stack of carrot each. ALL villages in this world on the realm are not breeding. Loading this world locally the villagers immediately start breeding. The realm has been closed and reopened a few times as well now.

I just uploaded the world to a bedrock dedicated server here at my house, and villagers breed there just fine. This bug seems to only be on our realm.

I downloaded a copy and I notice there are dozens and dozens of villages. I also see that coordinates display is enabled. Could you please give us approximate coordinates for somewhere the villagers don't breed? I'd like to inspect the village info.

Use this backup of the world, the other one is a few days older and doesn't have my village yet. The coordinates of my village is 1475 70 20

https://drive.google.com/file/d/1VPx7qd_TaIjHKzi0UvBs1anPV8rWxka5/view?usp=sharing

I downloaded your latest backup and loaded it into my realm. I then confirmed that your villagers would not breed even after I fed each of them a stack of bread.

Then I noticed your world has 2 resource packs and 4 behavior packs activated. When I disabled them and rejoined the realm, the villagers bred right away. So it appears you have an add-on that interferes with villager behavior.

Mojang cannot help you with defective add-ons it doesn't own. Unless you can reproduce this problem with no add-ons installed, I will have to close this report as Invalid.

Why is this only an issue on realms? 

If you provide a way to have add-ons then your hosted service should be able to support them just like other solutions. The realm is the cause here not the add-on. This is proven by it working both locally and on dedicated servers. 

I don't know why it only affects Realms, and it doesn't matter anyway. There are differences between the local server, the BDS server, and the Realms server, even though they're all generated from the same codebase and are 90% identical. Maybe the add-on author didn't do sufficient testing against 1.16 on Realms, or maybe they don't intend to support 1.16 on Realms, or maybe they already do support it and you just need to update to a new version of the add-on. Mojang doesn't know anything about any of that; that's for you and the add-on authors to work out. And if it turns out that the author discovers that the problem is a bug in Minecraft, it's up to them to create a bug report telling Mojang what part of the add-on interface isn't working properly. Until that happens, Mojang can't do anything because it doesn't own the add-on code, could only guess at how it's meant to work, and can't legally modify it anyway.