Hi there! Now when I use Coda’s app for iPhone, I’m always getting the error below whenever I run the app and try to open a page different from the one where it initially opened. I’m on a Iphone Pro 14 and iOS 18. Are you guys aware of this? It makes the iPhone app impossible to use. Thanks for any help!
1 Like
It seems that this was related to a memory issue in iOS 18, now solved with iOS 18.0.1 Whoever has the power to archive topics, please do so for this one. I didn’t figure out how to archive or remove my own topic. Thanks!
I am having the same issue and have already updated to iOS 18.0.1. When I attempt to look at the doc statistics on desktop, it doesn’t show that I have too many formulas or suggest any tweaks that are mentioned in the article here about slow docs.
I am willing and ready to listen to any techniques that will help my doc run better and be more accessible to my team.
It’s actually still happening with me too. It only worked at first after the update to iOS 18.0.1. But now 90% of the times I open the app, I get that error. Basically I’m not able to use the app at the moment, and this is already lasting for some weeks now… If it doesn’t get solved, unfortunately have to consider moving back to Notion again. No point in having a personal management system that only works in a laptop. Any Coda staff working on getting this solved?
I’m using iOS 18.1 on a iPhone 15 Pro Max and it is happening to me. It is unusable.
1 Like
Still the same with me as well… very annoying
1 Like
The app is unusable for me too. Really would like an update on work being done to solve this.
@Frederico_Ferreira , @Nathan_Velders , @Antonio_Martin1 , @Phil_Purdy1
Have any of you reported this to Coda support via the “?” bottom right of your screen? Or reported to Apple, seeing their latest IOS upgrade seems to be a common factor here?
I have a couple times. But the prompt doesn’t come up for me anymore.
Man, this just started affecting me to. I can’t even open my meal planning / grocery list on my iPhone 14 Pro. This is unreal.
Support doesn’t offer any solutions beyond downsizing the doc in my case.
Anyone know if this can be resolved by scaling up hardware from a processing power or RAM standpoint?