Uploaded image for project: 'Minecraft Realms'
  1. Minecraft Realms
  2. REALMS-5459

"Replace World" button not working with mobile worlds.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16 (Bedrock)
    • None
    • iPhone 8, 64 GB
    • Unconfirmed
    • Bedrock

      I recently purchased realms plus on my iPhone 8. I have been working on a world for roughly a year now and was pretty excited to upload the world to a realm. To my disappointment, my realm would not replace the realm with the message "An Error has occurred". 

       

      I have tried:

      • Transferring the world to my PC and doing it on the windows 10 edition
      • Logging out and logging back in to my Xbox Live account 
      • Closing and opening my realm to refresh it
      • Purchasing a completely new realm (still did not work)
      • Resetting the realm and uploading it

      However, the problem still persists and I am currently unable to upload it.

       

      How do I know it's only a problem for mobile players?

      I have asked many other mobile realm owners who experienced the same issue. However, Windows 10 players were able to upload theirs after a few tries.

       

      I also transferred my mobile world to my PC which still didn't work. However, all my worlds on windows 10 worked perfectly and were able to upload onto the realm.

       

      Also, I went onto a website that allows you to download worlds into your own game. I realized pretty quickly that every map made on mobile would not upload onto the realm. HOWEVER, all the maps made on windows 10 edition worked PERFECTLY.

       

      I have also found online that this is an extremely common issue.

       

       

      Thank you for reading my message. Please fix this ASAP because I am not the only user experiencing this issue. as shown above.

       

            Unassigned Unassigned
            vnticmc ryan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: