ios – How you can adjust to Apple’s “describing use of required cause API” when utilizing Firebase Crashlytics in a Flutter app?

After 1st Could 2024 apps submitted to Apple’s App Retailer should adjust to Describing use of required cause API. Whereas getting ready my Flutter app to satisfy these necessities I couldn’t learn how to do that when utilizing Firebase Crashlytics. Particularly this half is troubling me (quoted from the above hyperlink):

Disk house APIs

…

7D9E.1

Declare this cause to incorporate disk house data in an elective bug report that the particular person utilizing the gadget chooses to submit. The disk house data have to be prominently exhibited to the particular person as a part of the report.

Data accessed for that reason, or any derived data, could also be despatched off-device solely after the person affirmatively chooses to submit the particular bug report together with disk house data, and just for the aim of investigating or responding to the bug report.

Firebase Crashlytics does acquire and ship data like this, if I examine some present occasions within the Firebase Console, I can see RAM free amongst different gadgets underneath the Knowledge part of an occasion.

If I perceive appropriately it’s not sufficient to ask for the person’s permission to ship bug report knowledge on the whole. In keeping with the quote above I’ve to particularly ask for permission on every bug report and in addition show the content material of the report, together with free reminiscence.

How to try this with Firebase Crashlytics in a Flutter software? (Crashlytics itself is correctly added to my app and works effective, I can see check and actual bug experiences within the console.).

1. I do know that I can disable automated Crashlytics knowledge assortment about bugs and change it on and off for a particular person as detailed right here.

2. I do know that if I disable automated assortment I can examine for unsent Crashlytics experiences utilizing checkForUnsentReports.

3. I do know that relying on the person’s alternative I can both ship the experiences with sendUnsentReports or delete these utilizing deleteUnsentReports.

I attempted to implement the answer primarily based on the earlier steps and I used to be anticipating that I’ll have entry to all the knowledge collected within the bug report, together with free house. My plan was to show these to the person as required by Apple and supply the selection to ship or discard the bug experiences.

But it surely turned out I can not entry this data, I can solely ship or delete all unsent bug experiences.

I additionally tried to get this data from the place my code calls FirebaseCrashlytics.occasion.recordFlutterFatalError and FirebaseCrashlytics.occasion.recordError, however I discovered I can get solely the error particulars and stacktrace from right here.