/locate Fortress Not Actually There

I'm unable to reproduce this issue because you didn't mention the fortress coordinates in your description. They may have been given in your attachments, but I'm unable to open .HEIC files in Windows 10.

It's possible your problem is caused by changes in where fortresses are generated after the Nether Update. This kind of problem happens whenever an update involves changes to world generation. Because this changes terrain and biomes, structures that before the update were, or could be, generated at certain locations can no longer be generated at the same locations after the update. When this happens it's possible to get a mixture of old and new generation chunks in areas around the edges of where you've explored, which can leave the terrain distorted and structures missing or disfigured.

If this is what is causing your problem, it can't be fixed because the only way to do that would be to disallow any future changes to world generation, which means no more big updates. However, these problems are limited to the edges of previously explored areas and shouldn't affect your worlds farther out, nor should you encounter it in worlds you created after the update.

Does this sound like it might be the explanation of what you've observed? Or are you seeing a similar problem in new worlds or areas where you're certain you've never explored within view of? If you create a new world with the same seed, is there a fortress at the coordinates given in the command output?

This ticket is being temporarily closed as Awaiting Response. It will reopen automatically if you reply.

So sorry about that! I re-uploaded the images as .jpg files. The Fortress coordinates are supposed to be at 224, y, -80. I believe I had previously explored that area before the Nether update, so maybe that's the issue. When I created a new world with the same seed, I did not find a Fortress at that location, although when I tried /locate Fortress in this new world, it did not say there was one at 224, y, -80. 

Thanks for responding and replacing the screenshots.

The seed in your first screenshot doesn't match the one you gave in the description, where you gave it a "3" instead of a "2" in the 7th digit position. You probably used the wrong seed when you created the new world, and that's why there was no fortress there and why /locate gave you entirely different coordinates.

When I used the seed to create a new world, /locate gave me the same coordinates (224, y? -80). I went to 1800, 68, -640 in the Overworld (essentially the corresponding Overworld position), built a portal and went through. I came out in the Nether at 221, 60, -72, right next to the little lava pool with no floor that marks the center of the fortress. So /locate was giving you the coordinates as if the chunks were generated in the new release, but in fact they were upgraded chunks from the earlier version. That corroborates my theory from before.

So I think everything is working the way it's meant to. As I said before, this issue can't really be fixed without making it policy not to change world generation in new releases, and I'm pretty certain Mojang won't consider doing that. We'll pass this along to the developers anyway, because it's their prerogative to say they can't fix it, but I wouldn't hold my breath waiting for a fix.

Oh okay I see, that's too bad. Well, thanks for all your help!

I forgot that we already have a ticket describing the same issue and resolved as Won't Fix, so I'm closing this one as a duplicate MCPE-84772.