I created a pretty basic rocket animation recently to add into my team's Unity game. When my developer imported the JSON files, he got the error "Could not automatically set the AtlasAsset for "skeleton". When selecting "Resolve atlases..." the subsequent error, "SkeltonDataAsset for 'skeleton' has missing regions", appeared. Browsing and selecting the atlas manually leads us through the same cycle again.

This issue doesn't make sense since I've used the exact same export settings as past animations that worked out just fine. On a quest to figure out how to resolve the issue, I've tried out the following:

• Exporting in the newest version of Spine
• Exporting using Spine 3.8.99 (Unity is using Spine 3.8 )
• Exporting using Spine 3.8.95
• Exporting on a different computer
• Ruling out whether the animation file is corrupt by recreating the animation (it's a simple one afterall)
• Double checking if I am using .atlas.txt
• Added a 3% opacity background to my images because I heard there can be an error if there is too much empty space..
• Turned on/off white space
• Turned on/off flattened path
• Made absolutely sure that there are no improperly named files that are not linked correctly
• Tried renaming all the files just in case.
• Made sure that there are no empty files, slots, etc.

Nothing is working. I've had another Spine animator that we work have a look and he's also unable to find a solution.

Maybe someone can have a look at the files we're using and identify the issue? This folder contains the Spine file, the image folder, as well as one of the many sets of JSON export files we tried importing into Unity.
https://drive.google.com/drive/folders/1KEbwQ9JqfKGczFi1Dopoe_Jcl10-q2IU?usp=sharing

Thanks for the quick reply. Interesting to see that it worked on your side. That certainly begins to narrow down where the problem might be.

Which Unity version are you using? We are using Unity 2020.1.17f. All other animations are working fine except this one.

Contents of version.text:

This Spine-Unity runtime works with data exported from Spine Editor version: 3.8.xx
Package version: spine-unity-3.8-2020-06-25.unitypackage

As mentioned, we're already using the latest version of Spine within Unity. You mean to say that we are running into the issue because we are using Unity 2020.17f? And you're suggesting that by upgrading to Unity 2020.2, we may be able to resolve the problem?

Is this our only hope until the remaining bugs for the higher versions of Unity get resolved?