search

corona-warn-app / cwa-app-ios

Native iOS app using the exposure notification framework from Apple. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
1.68k stars 285 forks source link

High storage comsumption for personal data #2806

Closed FlightMS closed 2 years ago

FlightMS commented 3 years ago

Avoid duplicates

Technical details

Describe the bug

The app seems to be have a high storage comsumption. As you can see in the screenshot, it needs ~131 MB for personal data.

Is that a normal amount for the app?

Steps to reproduce the issue

  1. Open Settings app
  2. Check storage management for the Corona-Warn-App

IMG_6560

Expected behaviour

Less more storage used for personal data by the app.

Possible Fix

Additional context

Internal Tracking-ID: EXPOSUREAPP-7589

Ein-Tim commented 3 years ago

Hey @FlightMS

Thank you for reporting this issue. Do you see this behavior since a special CWA/iOS version? We had a similar issue before, #1549, this was fixed back in version 1.9.

On my iPhone CWA's "Dokumente & Daten" are ca. 70 MB, you have nearly twice of this, so I don't think this is normal. Do you have a test registered, many check-ins or contact diary entries?

FlightMS commented 3 years ago

I saw this the first time when I created the screenshot yesterday. Before I've never checked the storage consumption before. So I can't say if the problem occurs since a specific version.

I have one registered Rapid Test (the first ever), some contact diary entries (not very much - only a few days), some QR Code check-ins and 12 places and 4 persons.

heinezen commented 3 years ago

@FlightMS

Interesting. Thanks for reporting this to us. The dev team will have a look at this.

Corona-Warn-App Open Source Team

Ein-Tim commented 3 years ago

@FlightMS One more question, did you activate the new error logging feature in the app?

FlightMS commented 3 years ago

@Ein-Tim No that's not activated

FlightMS commented 3 years ago

„Dokumente & Daten“ are still increasing on my iPhone. Now it‘s about 212,2 MB.

Ein-Tim commented 3 years ago

I'll now start logging my numbers here:

iPhone XR:

iPhone 6s:

Ein-Tim commented 3 years ago

@thomasaugsten

You said back in https://github.com/corona-warn-app/cwa-app-ios/issues/1549#issuecomment-737714790 that iOS doesn't automatically "clean up temporary system files of the app" and that you "add a feature to trigger this system clean up manually", is this still in place and works?

dsarkar commented 3 years ago

@FlightMS @Ein-Tim Thanks for the update. Forwarded into the internal ticket.

Ein-Tim commented 3 years ago

11 days have passed since my last comment and here are my new numbers:

iPhone XR:

iPhone 6s:

FlightMS commented 3 years ago

I can also share my new numbers here:

On my iPhone 11 „Dokumente & Daten“ is now about 221,2 MB with version 2.6.2. I‘ve entered one rapid test result and scanned one check-in QR code within the last 14 days.

Ein-Tim commented 3 years ago

@FlightMS

Please update to the latest CWA version & iOS 15 and let us know if anything changed.

FlightMS commented 3 years ago

@Ein-Tim

No change here. I‘ve stopped scanning codes and entering data in the contact journal some time ago.

BCEF0851-7D1D-4E03-8B6D-A9ACBD6397A1

dsarkar commented 3 years ago

@FlightMS Thanks for the feedback. The information was forwarded to the internal ticket. CC @Ein-Tim Thanks.

FlightMS commented 2 years ago

Time for some updates. Just right now this is my space used with my iPhone 11 and iOS 15.2

9887B5C4-DF0B-44EF-BB56-8D7648AE2541

dsarkar commented 2 years ago

@FlightMS Thanks for update, forwarded to internal ticket.

FlightMS commented 2 years ago

Seems something happened here

A927248C-5AAB-4B8D-84EF-6BCD91C33886

Ein-Tim commented 2 years ago

This issue is fixed for me: image

@FlightMS Can the issue be closed?

FlightMS commented 2 years ago

@Ein-Tim thanks for the confirmation.

Issue closed

dsarkar commented 2 years ago

@Ein-Tim @FlightMS Thanks for the feedback, which I forwarded to the internal ticket.