Ae crashing when playing back animation on Mac sequoia 15.5 Ae version 25.3.2

Issue seems to have resolved somehow - thank you!

- also just to add, i've managed to repair the issue with the adobe app and have tried downgrading to 25.3.1 and I have good moments and bad with it, ranging from 5mins to 2hrs working without a crash.

I have actually tested this file on 4 different macs - one a brand new higherer performance machine than mine. All seem to be responding the same.

Wouldn't be the first time though that only one thing was changed in ae/prem but it actually brought along other things with it aha. But yeah idk what else I can say other than the issue only happened when I updated two separate machines and instantly vanished as soon as they were downgraded.

@SophieIKB I'm wondering if your machine is in a bad state overall given your comment about Creative Cloud not even loading for you? We are looking at the issues reported via the log, but it is somewhat unclear how AE is getting into that state. 

@Tom_edit There is only 1 change in 25.3.2, which is related to the use of Encrypted PDF files. Not sure how going back to 25.3.1 would fix that. Also not sure if it's related to this post? 

EDIT: I see now you are referring to the other error dialog Sophie posted. 

When i try to close it manually, i tend to get a spinning wheel so I've had to force quit. I've been doing it a lot so I might have got into auto pilot doing it as i've noticed it sometimes says its not responding and other times its OK.

I've been trying to use an old version of Ae, however my creative cloud app is showing a blank screen and i cannot find a way to use an old version via the web version. An y advice on how I can downgrade? Thank you both for all your help so far 🙂

@jenkmeister17177426  I also immediately ran into the 

After Effects error: internal verification failure, sorry! {no current context}

error dialogue box posted above, it didn't really stop me from working, but it got really annoying and it kept throwing other errors at me so I eventually downgraded back to 25.3.1 to make it go away. I know that's not super helpful, sorry, but just wanted to chime in to say that's not an isolated issue

Thanks. I do see a couple of issues towards the end which I'll have some of the team look at. 

As an aside, is there a reason you force quit at the end? Is it because the Quit in the menu isn't working when you get the issue happening?