Backwards Compatibility

Question

Created 2h

Replies 1

Boosts 0

Participants 2

No technical justification is strong enough to erase months of developer work through incompatible project migrations without a reliable upgrade path.

Reality Composer Pro has evolved quickly, but projects built around timelines, behaviors, transforms, spin, orbit, hide actions, and synchronized audio represent hundreds of hours of creative work. When those projects import with missing actions or stripped timelines, the cost isn’t just technical—it is developer time, money, and eduction that cannot be recovered.

Please prioritize migration tools or compatibility layers that preserve existing timeline projects. Backward compatibility is not just about code; it is about respecting the investment developers make in your platform.

Xcode 27 Beta 2
Reality Composer Pro 3
Import reports:
- Missing Transform To
- Missing Transform By
- Missing Spin
- Missing Orbit
- Missing Hide
- Missing timelines and behavior
- Audio synchronization no longer present 60 others. Basically any movement or action.

For a new developer, this isn’t the loss of a feature. It’s the loss of two years of blindly learning, invested in a workflow that no longer exists. That work now survives only in memories of an app that never had the chance to be approved. Can i revert to the previous version?

Thank you for any replies and the time taken.

Answer 1

Etresoft OP

1h

Can i revert to the previous version?

Why not?

The only thing you really have to be concerned about is Apple's requirements for submission to the App Store. As of April 28, 2026, you must use Xcode 26 to submit apps. It seems likely that there will be a similar updated requirement next year.

If you're stressed for time, then don't install beta software. You'll still have six months or so to get used to the new versions when everything gets released. Hopefully they will be working better by then.

Also, there is a beta version of Reality Composer Pro available too. There is a case to be made for getting familiar with the betas and submitting bug reports if you encounter serious problems. Ideally, you can continue development with stable versions on production device while also testing beta versions on test devices. In this case, that may mean a dedicated Mac and dedicated test devices.