After 1st Might 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 the way 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 info in an elective bug report that the particular person utilizing the machine chooses to submit. The disk house info have to be prominently exhibited to the particular person as a part of the report.
Data accessed because of this, or any derived info, could also be despatched off-device solely after the consumer affirmatively chooses to submit the particular bug report together with disk house info, and just for the aim of investigating or responding to the bug report.
Firebase Crashlytics does gather and ship info like this, if I verify some current occasions within the Firebase Console, I can see RAM free amongst different objects underneath the Knowledge part of an occasion.
If I perceive appropriately it’s not sufficient to ask for the consumer’s permission to ship bug report information normally. 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 advantageous, I can see check and actual bug experiences within the console.).
-
I do know that I can disable automated Crashlytics information assortment about bugs and swap it on and off for a selected consumer as detailed right here.
-
I do know that if I disable automated assortment I can verify for unsent Crashlytics experiences utilizing checkForUnsentReports.
-
I do know that relying on the consumer’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 information collected within the bug report, together with free house. My plan was to show these to the consumer as required by Apple and supply the selection to ship or discard the bug experiences.
However it turned out I can not entry this info, I can solely ship or delete all unsent bug experiences.
I additionally tried to get this info from the place my code calls FirebaseCrashlytics.occasion.recordFlutterFatalError and FirebaseCrashlytics.occasion.recordError, however I came upon I can get solely the error particulars and stacktrace from right here.
