Closed WeiLingQiang closed 6 months ago
Thanks for reaching out. I'm checking,
I've been trying to reproduce this issue but it's limited to force crash. Are you running into similar issues when causing a crash on the native layer in a different way?
I haven't tried different ways to Crash. Can you provide an example?
I try to call Throw: Object C
、ThrowCpp
All are calling interfaces in demo
Why is it collected:
WatchDogTermination
The olminedog terminated your app, posssiBly BeCAUSE it overused ram.
The demo includes samples and snippets to C/C++ crashes. You can find them in 2_NativeSupport
scene.
I expect them to work properly.
The watchdog termination is something specific to the Apple platforms and based on heuristics. We have some documentation here going into more details
For WatchDog Terminings, I don’t quite understand, Can I close it so that it can show the Crash Stack normally?
The watchdog termination is a different kind of issue. The operating system terminated the app and the SDK makes an educated guess as to why that happened.
Excuse me, Whether iOS supports EnableBitCode = NO ?
Bitcode has been deprecated by Apple and can be ignored.
Why parside the Crash of iOS is a symbol table generated by BitCode?
If I set up bitcode = no, I can't find the symbol table analysis
I'm not sure what it is that is not working for you. The way it is set up right now sentry cli will only upload debug symbols if bitcode = no
.
I use the sentry-cli command line to upload manually, is it correct?
Test results: Just upload the symbol table as shown in the figure (generated by BitCode) The three symbols generated by non-BitCode are useless
It looks like it is working out for you?
Yes,bitcode = yes
effective for me,and the bitcode = no
cannot analyze the Crash log
My problem has not been solved yet,I need to set up bitcode = no
, but this has caused it to be unable to analyze the Crash stacktable
The screenshot shows that there are uploading symbols, but there is no normal analysis Crash stack
I have to correct myself. The SDK dropped checking for bitcode
in version 1.5.0
. The SDK adds a script to the build phase that will automatically upload the relevant symbols for you.
Could you provide me with a small repro so I can test what's going on locally?
Why is the marking of the symbol table in the red box unusual?
Environment
How do you use Sentry? Sentry SaaS (sentry.io) or self-hosted/on-premise (which version?)
Which version of the SDK? 1.7.1
How did you install the package? (Git-URL, Assetstore) Git-URL, UPM
Which version of Unity? Unity2021.3.26f1
Is this happening in Unity (editor) or on a player like Android, iOS, Windows? iOS
Steps to Reproduce
UnityEngine.Diagnostics.Utils.ForceCrash(ForcedCrashCategory.FatalError);
There is a problem with the Crash stack analysis,Unable to parse the Crash log stack Symbol has been uploaded
Any logs or screenshots