You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently experiencing an out-of-memory crash on iOS in production (app store). The Crash Logs provided by Apple hold symbols from the Flutter Engine, although do not give any context of where the error is happening. Can Firebase Crashlytics provide a way to catch these types of errors? I've also attempted to find any memory leaks running on a physical device on a release build running the same iOS version with no obvious memory leaks.
Would this code work in the instance of an out-of-memory crash?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am currently experiencing an out-of-memory crash on iOS in production (app store). The Crash Logs provided by Apple hold symbols from the Flutter Engine, although do not give any context of where the error is happening. Can Firebase Crashlytics provide a way to catch these types of errors? I've also attempted to find any memory leaks running on a physical device on a release build running the same iOS version with no obvious memory leaks.
Would this code work in the instance of an out-of-memory crash?
Beta Was this translation helpful? Give feedback.
All reactions