What is the solution for resolving EXC_BAD_ACCESS (code=2, address=0x16dbd3fd0) when using stack-based navigation with many registered paths #3162
Replies: 3 comments 7 replies
-
Hi @Chang-Geun-Ryu, well, that is quite the complex feature. 🙂 There's a chance that it's just not possible to have that many features in a path, but in order for us to experiment with a fix we would need a sample project that reproduces the problem. Can you help us with that? |
Beta Was this translation helpful? Give feedback.
-
Did run into same issue. As a temporary workaround combined/reused some feature flow loading screens to reduce number of path cases. Generated an example. Just press 'Push' Running on an iPhone 12, iOS 17.5.1 Edit: when I build it in release configuration for Instruments, it runs fine 🤷♂️
|
Beta Was this translation helpful? Give feedback.
-
My case is the same. Additionally, it doesn't reproduce in the release version and simulator. This issue is even more confusing since it started occurring after updating to 1.12.1. |
Beta Was this translation helpful? Give feedback.
-
In my case, targeting iOS 17 and using Stack-based navigation, the issue occurs when I register 41 "@Reducer enum Path" instances, the app works fine, but when registering 42 instances, I encounter EXC_BAD_ACCESS (code=2, address=0x16dbd3fd0).
Is there a limit to how many more I can register?
Beta Was this translation helpful? Give feedback.
All reactions