Without that, there's two ways to do this with major drawbacks:
Background tasks (android supported-ish with iOS support only with app open): Apps like Thunder are doing partial implementations by essentially polling the lemmy server in the background. I don't think this is very neighborly because it puts a strain on Lemmy instances with the polling per account every 15 mins. It also consumes more battery. And is not consistent depending on Android device manufacturer.
Storing JWTs on a server: Some apps do this, but this is a nonstarter for me due to security/liability reasons
So IDK. Right now I feel pressure to do this because other apps support but the ways they are accomplishing this are pretty questionable.
The cache is 100% Apple/iOS code that should free up if you're running low on device space.
I researched a bit ago and it is possible to force clear, I think, but its a low priority because it's not a bug, it's iOS using unused device space for caching.
Really the bug is that cache is exposed as 'used space' in the interface anyways. iOS should show cache as free space (because it just gets cleared when you need the space anyways).
Currently the deploy process to the stores is completely automated through Ionic AppFlow. If there's a way to automate deployment to this store I'd be happy to add!
Voyager just checks for the "cross-posted" in the body of the post. Its not perfect though. If its a non-lemmy post, it will fail currently. Also if the post isn't resolved then it will fail.