After uploading a world to a realm while a behavior pack is attached, the behavior pack fails to do anything once the realm is open.

I've created my own behavior pack which adds a few custom blocks, a few custom items, and an ever growing list of recipes. I've made sure the behavior pack functions properly on normal worlds before trying to upload it to the realm. I've also updated all of the manifests to have new UUIDs as well as the actual behavior pack version. The resource pack is attached through the manifests dependencies and also has new UUIDs and updated versions. This is all being used for an adventure world I'm co-creating with my girlfriend. It needs to work on the realm in order for her to use the behavior pack since she can only play on her Xbox.

Once logged into the realm, none of the blocks or items appear in the crafting menu or the commands list. The recipes also cease to exist. I've gone as far as adding the behavior pack directly to the world file and still nothing works. I also want to throw out a little fact that I found concerning. When using the behavior pack on normal worlds, I'm prompted with a notification asking if I'm ok with the behavior pack running scripts on my device. This is fine, if I had added scripts, but I've done no such thing, so why is it prompting me with this? It also did the same thing on the realm when I added the behavior pack to the world files but the behavior pack still didn't work on the realm. This same issue made it impossible for my girlfriend to join the realm until I pulled the world down and removed the behavior pack before re-uploading it to the realm.

This appears to be an old issue and is either classified as "resolved" which it isn't, or is unacknowledged. This is an example of what I'm referring to: REALMS-1878

I'm aware of the fact that you guys don't like us creating new tickets for bugs that have already been reported, but I'm not afraid to make a lot of noise if it means I get some acknowledgement. So you can expect a new ticket for this same issue once a week until the end of august. If I haven't received some kind of acceptable answer by then I'll start making new tickets twice a week. And all you have to say is "we're working on it". And preferably include an approximate resolution date. I've included my behavior pack and resource pack for reference. These are still in development, but are problem free.