Lack of clarity regarding Crashlytics deobfuscation with Flutter

[roblframpton]

I am really struggling to follow the status of Crashlytics deobfuscation with Flutter.

• This part of the Crashlytics documentation states that I should use the firebase crashlytics:symbols:upload command to upload my debug symbols. Confusingly, this page also says that split-debug-symbols is not supported for iOS, although comments on GitHub state that this is outdated information.
• Meanwhile, this part of the same documentation suggests that symbol upload is handled automatically by Gradle on Android and an XCode build script on iOS. It never mentions the symbols:upload command from the other page so it's unclear if they do the same thing or not.
• There are numerous lenthy discussions on GitHub about Dart deobfuscation on Crashlytics, but after re-reading many times it's difficult to get a definitive answer about whether it is fully supported yet.

In my particular case I am trying to use both commands, but on iOS the upload:symbols command gives me same error as this issue, although that was closed in favour of another issue concerning the obfuscation of Dart code, never mentioning the error. But from the discussion on GitHub, I'm not even clear about whether I'm supposed to use this command at all.

So, I would really appreciate it if someone could provide an answer to the following questions:

• When configured correctly, does the Gradle build automatically upload symbols allowing for the deobfuscation of Dart code? Or just native code?
• When configured correctly, does the XCode build script automatically upload symbols allowing for the deobfuscation of Dart code? Or just native code?
• What is the difference between the above two and the symbols:upload command?
• Should I expect the symbols:upload command to succeed without an error for iOS symbols, or not?
• Should I be ignoring one of the two documentation pages linked above? Which one?
• As of now, if my app is configured correctly, should I expect to see obfuscated Dart stack traces on Crashlytics for both Android and iOS? Or is this still in progress?