PanchoLopez At this point, I would consider the possibility that this is not GrapheneOS-specific and that the app just hasn't been properly updated to support Android 14. Check for people on stock Android 14 reporting similar issues.
People often mistake app developers not fixing their apps for new releases as GrapheneOS issues because we're very fast in upgrading to new Android versions, and most people are still on the previous, and are therefore unaffected.
This happened with Session messenger very recently, where people thought there was an issue with GrapheneOS, but Session just wanted supporting Android 14 correctly.
I'm not ruling out there being something specific to GrapheneOS here, by the way, I'm just saying that you might want to explore that possibility.