Based on the contexts provided and your description, it seems like the issue might be related to version mismatches or incorrect export settings. When exporting and importing JSON files in Spine, it's crucial that both parties (you and the developer) are using compatible versions of Spine and have correctly set up the export settings. The contexts suggest various potential issues, such as missing animation events, incorrect skeleton data, or problems with attachments not being properly imported or exported.
One common theme across several contexts is the importance of ensuring that the Spine Editor version matches the Spine Runtimes version being used for development. For example, if you are using Spine 4.2.09-beta, the developer should also use a runtime compatible with this version. Additionally, when exporting, make sure that all necessary data is included in the JSON file, such as attachments and animations. If you're adding new bones and attachments, ensure that these are correctly referenced in the JSON file and that no data is missing.
Given that the accessories and the new bone you added are not appearing as expected, it's possible that there was an issue with the export process, such as missing data or incorrect settings. It's also possible that the developer's runtime version might not fully support the features used in your Spine version, especially if you're both using a beta version, which might have specific compatibility considerations.
To troubleshoot, double-check that both you and the developer are using fully compatible versions of Spine and its runtimes. Also, review your export settings to ensure that all necessary data is included. If the problem persists, consider exporting the project again and verifying that all attachments and bones are correctly set up in Spine before exporting.
