Closed irwinOT closed 4 years ago
cc @cyanglaz
@mraleph
@cbracken can somebody on the Flutter team symbolize this crash?
@mraleph @irwinOT I don't think anyone other than the app owner can symbolicate this crash log without a dSYM. Maybe you can follow this to try to symbolicate the crash? As much as I want to help, without a symbolicated crash log, it is very difficult to know what's going on.
@cyanglaz Flutter framework is prebuilt so Flutter team should have dSYM
for it. Unless of course those are not archived - which would be a pity.
They are in fact archived: instructions are here https://github.com/flutter/flutter/wiki/Crashes
I went ahead and symbolicated Flutter frames using dSYM from engine build 3757390fa4b00d2d261bfdf5182d2e87c9113ff9
$ atos -arch arm64 -o Flutter.dSYM/**/Flutter -l 0x10141c000 0x000000010144fa84
fml::DataMapping::~DataMapping() (in Flutter) (mapping.cc:15)
$ atos -arch arm64 -o Flutter.dSYM/**/Flutter -l 0x10141c000 0x0000000101497318
shell::Shell::Create(blink::TaskRunners, blink::Settings, std::__1::function<std::__1::unique_ptr<shell::PlatformView, std::__1::default_delete<shell::PlatformView> > (shell::Shell&)>, std::__1::function<std::__1::unique_ptr<shell::Rasterizer, std::__1::default_delete<shell::Rasterizer> > (shell::Shell&)>) (in Flutter) (shell.cc:209)
$ atos -arch arm64 -o Flutter.dSYM/**/Flutter -l 0x10141c000 0x0000000101429720
-[FlutterEngine createShell:libraryURI:] (in Flutter) (FlutterEngine.mm:360)
$ atos -arch arm64 -o Flutter.dSYM/**/Flutter -l 0x10141c000 0x0000000101437bec
-[FlutterViewController initWithProject:nibName:bundle:] (in Flutter) (FlutterViewController.mm:75)
Unfortunately this symbolication is not that helpful to me (e.g. I don't think the code in question can actually call DataMapping::~DataMapping
, I think this is just code deduplication where multiple destructors with the same body ended up at the same address in the binary) - but somebody with Shell
knowledge (@chinmaygarde ?) might be able to reason what exactly went wrong.
@cyanglaz @cbracken See how this incidence can be reproduced (I have already done it with 3 different devices and three different devices):
We cannot reproduce this as reported. If you are still seeing this, I recommend trying a new host machine, a new device, and a newer version of Flutter. If you're still seeing it then, please provide precise steps to reproduce in a new bug with extreme detail.
@irwinOT I am facing the same error. Do you manage to solve it?
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v
and a minimal reproduction of the issue.
First, sorry for my english.
Second, I put the question on stackoverflow.com but I have no answer.
In development it was tested and worked well, both in Android and in iOS. A production .app was generated, apple app store was sent and an error occurred:
Apple Message: We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue.
Apple Log:
FLUTTER DOCTOR: