-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AEPCore 5.0.0, AEPAnalytics 5.0.0 crashes #1025
Comments
@niorko Can you share the full crash reports for all of these different crashes? We need to see the full stack trace (all threads) to have a better idea of whats going on considering you don't have steps to reproduce. Thanks. |
Hello, I can't download full stack crash report from Crashlytics, but I gathered few crashpoints from Xcode Organizer from the past two weeks. I hope it helps. Thank you |
@niorko Looking at all the crash logs, it seems to be some kind of memory corruption. I can't conclusively pinpoint where the actual corruption happens. Do you see similar crashes outside of AEP SDK? Can you also turn on memory management diagnostics for your app and see if you can catch any errors? |
@praveek I haven't seen any leaks nor corruption and I can't induce the situation, because it does not happen regularly. The only thing that I have in regards with crashes are these crashes from Firebase Crashlytics and crashes in Xcode Organizer. :( |
@cdhoffmann is there any progress? I am being asked constantly on this issue. Thank you. |
Prerequisites
Bug summary
We observe around 6000 crashes on Firebase Crashlytics that are marked as issue with AEPCode and other latest versions of Adobe Analytics.
These are the examples of stack traces:
Environment
iOS: 79% iOS 17, 18% iOS 16, 2% iOS 15
SDK: AEPCore 5.0.0 (21E210), AEPAnalytics 5.0.0 (21E210)
IDE: Xcode 15.3.0
Steps to reproduce
Unable to reproduce - around 6000 crashes catched on Firebase Crashlytics.
Current behavior
It crashes.
Expected behavior
To not crash.
Anything else?
No response
The text was updated successfully, but these errors were encountered: