Batwoman: Ruby Rose quit CW show ‘due to tension on set over long hours’

The decision had nothing to do with her health or injury

Annie Lord
Thursday 21 May 2020 13:07 BST
Comments
Trailer for Batwoman series

The reason behind Ruby Rose’s surprising departure from the Batwoman CW series has reportedly been revealed.

On Wednesday (20 May), Rose announced she had quit the series to the surprise of the show’s fans.

“This was not a decision I made lightly as I have the utmost respect for the cast, crew and everyone involved with the show in both Vancouver and in Los Angeles,” she said in a statement without citing any reasons.

Multiple sources have now told Variety that there was tension on set because Rose was unhappy with the long hours required of her. As a result, Rose, CW and Warner Bros Television mutually agreed to part ways.

Previously it was speculated that Rose’s exit had something to do with the emergency surgery Rose underwent for two herniated discs, but one source told Variety that Rose’s decision “had nothing to do with her health or injury”.

Last year, Rose opened up about how mental health issues. She captioned an Instagram photo “I’ve struggled with mental health my entire life” before speaking out about her struggles with misdiagnosis and PTSD.

Announcing her decision to leave the show, Rose said: “I have made the very difficult decision to not return to Batwoman next season.”

“I am beyond appreciative to Greg Berlanti, Sarah Schechter and Caroline Dries for not only giving me this incredible opportunity, but for welcoming me into the DC universe they have so beautifully created.”

Brooklyn Nine-Nine‘s Stephanie Beatriz has already seemingly thrown her hat into the ring to take over from Rose.

Reps for Rose, Warner Bros and The CW declined to comment.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in