Firebase Crashlytics与R8混淆问题：控制台仍显示混淆堆栈跟踪

我遇到了Firebase Crashlytics和R8混淆相关的问题：控制台里始终显示混淆后的堆栈跟踪，但从构建日志来看，mapping.txt文件已经成功上传到Crashlytics API：

2023-09-08T10:46:40.132+0200 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Executing request PUT /v1/project/-/app/[redacted]/upload/java/[redacted] HTTP/1.1
2023-09-08T10:46:40.132+0200 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Target auth state: UNCHALLENGED
2023-09-08T10:46:40.132+0200 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Proxy auth state: UNCHALLENGED
2023-09-08T10:46:41.794+0200 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection can be kept alive indefinitely
2023-09-08T10:46:41.795+0200 [DEBUG] [com.google.firebase.crashlytics] PUT response: [reqId=null] 200
2023-09-08T10:46:41.796+0200 [INFO] [com.google.firebase.crashlytics] Mapping file uploaded: [redacted]/build/outputs/mapping/qa/mapping.txt
2023-09-08T10:46:41.796+0200 [LIFECYCLE] [org.gradle.internal.operations.DefaultBuildOperationRunner] 
2023-09-08T10:46:41.796+0200 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Execute uploadMappingFile for :app:uploadCrashlyticsMappingFileQa'
2023-09-08T10:46:41.797+0200 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Executing task ':app:uploadCrashlyticsMappingFileQa''
2023-09-08T10:46:41.738+0200 [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] 
2023-09-08T10:46:41.738+0200 [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] > Task :app:uploadCrashlyticsMappingFileQa
2023-09-08T10:46:41.796+0200 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Execute uploadMappingFile for :app:uploadCrashlyticsMappingFileQa' completed
2023-09-08T10:46:41.797+0200 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Executing task ':app:uploadCrashlyticsMappingFileQa'' completed

另外，本地使用R8 Retrace工具，结合该mapping.txt和从Firebase控制台下载的堆栈跟踪文件，能够正常完成反混淆：

// 此命令可正常执行并输出反混淆后的堆栈跟踪
./retrace [redacted]/app/build/outputs/mapping/qa/mapping.txt [redacted]/stack.txt

有人知道这是什么原因吗？另外现在Firebase控制台似乎不再支持手动上传映射文件，也无法查看已上传的映射文件了。

内容的提问来源于stack exchange，提问作者Niels Masdorp