I'm running iOS 13.6.1 on iPhone SE 2020. Installed Koronavilkku same day it was initially released. Now running 1.0.1 (232). Koronavilkku is not doing exposure checks periodically. The only check is done 3. Sep 2020 (6 keys). Tried to uninstall & reinstall the app and reboot the phone with no help. App seems to be in good state ("Koronavilkku käytössä").

I installed the app after updating iOS to 13.7. When I first opened the app I accepted the terms and continued. Then I got the system permission prompt about enabling exposure notifications and I chose Enable.

However on the main screen the app says "Koronavilkku ei käytössä" and tapping the button "Ota käyttöön" below it does nothing. Also if I try to enable exposure notifications from the settings I can tap "Ota käyttöön" button but after returning to the main settings page the status still says "Ei käytössä". I have tried both restarting and reinstalling the app, but to no avail.

Since Apple released the exposure notification support (at least used in Britain) for iPhone 6/5s in December (with the OS version 12.5) would it be possible for Koronavilkku to work on these older iPhones, too? https://www.bbc.com/news/technology-55317202

Koronavilkku reports a possible exposure. Nevertheless, all of the log entries (altistustarkistukset) for the past two weeks have zero key hits (avainosumien määrä 0). The timestamp of the newest log entry is after the exposure became visible in the app.

If I have understood correctly, an exposure can only be reported if there is match found between the keys in my phone and the ones on the server (from infected people). Thus, there should be at least one key hit in the logs.

• Device: iPhone 8
• OS Version: iOS 14.0.1
• Koronavilkku: 1.1.0 (289)

IOS own functionality shows that there's two key matches (avainosumien määrä) but Koronavillu app says that there's no matches ("Ei havaittu altistumisia" ja tarkistettu viimeksi: 2 minuttia sitten.).

I have rebooted IOS but no changes. app & phone info: Koronavilkku 1.0.1 (232) iPhone 11 Pro Max with IOS 14.0

The missing spacing becomes obvious at least in Swedish when using a particular screen width (iPhone 6 / iPhone X), when the word "som" comes too close to the checkmark. 20 points of offset would be enough to fix it, as seen on the right image.

Not sure if this is a bug since I'm not particularly familiar with the setup, but thought I'd report this just in case.

Settings > Privacy > Health > COVID-19 exposure logging > Exposure checks > Export

When viewing exposure checks on iPhone, we expected to see how many other devices using KoronaVilkku the phone has come into notable contact with, and is now checking for exposure as a result. This seems to report the same information regardless of user however. Not sure if this is a bug in functionality or just an oddity in reporting exposure check data, but checked keyCounts and hashes are identical between two iPhone users and one Android user in different locales in Uusimaa (albeit hash doesn't match in Android device).

iPhone 1 { "Build" : "17G80", "ExportVersion" : 1, "ExposureChecks" : [ { "Hash" : "FDD34C6170CB06668BE36457178908925ADE485B21366281981FE5BABD77C696", "RandomIDCount" : 6, "MatchCount" : 0, "DataSource" : "fi.thl.koronahaavi", "Timestamp" : "2020-09-03 07:20:17 +0300" }, { "Hash" : "7CA1AD8DA7964C70E4EA6903780CABC7F224209111F9F12AE0FB28065D864B5A", "RandomIDCount" : 19, "MatchCount" : 0, "DataSource" : "fi.thl.koronahaavi", "Timestamp" : "2020-09-04 08:48:21 +0300" } ], "DeviceProductType" : "iPhone8,2" }

iPhone 2 { "Build" : "17G80", "ExportVersion" : 1, "ExposureChecks" : [ { "Hash" : "FDD34C6170CB06668BE36457178908925ADE485B21366281981FE5BABD77C696", "RandomIDCount" : 6, "MatchCount" : 0, "DataSource" : "fi.thl.koronahaavi", "Timestamp" : "2020-09-03 07:42:58 +0300" }, { "Hash" : "7CA1AD8DA7964C70E4EA6903780CABC7F224209111F9F12AE0FB28065D864B5A", "RandomIDCount" : 19, "MatchCount" : 0, "DataSource" : "fi.thl.koronahaavi", "Timestamp" : "2020-09-04 07:24:22 +0300" } ], "DeviceProductType" : "iPhone8,4" }

Android {"timestamp":"September 3, 2020, 08:45", "keyCount":6, "matchesCount":0, "appName":"Koronavilkku", "hash":"\/dNMYXDLBmaL42RXF4kIklreSFshNmKBmB\/lur13xpY="}, {"timestamp":"September 4, 2020, 09:00", "keyCount":19, "matchesCount":0, "appName":"Koronavilkku", "hash":"fKGtjaeWTHDk6mkDeAyrx\/IkIJER+fEq4PsoBl2GS1o="}

Perhaps I'm expecting the wrong thing from Exposure Check reporting, feel free to close this if this is the intended functionality.

Hi!

I've had few colleagues wonder if there's going to be an English language version available soon? I took a look at the localization in this project at it seems that translating them shouldn't be a huge task, so is this something you would be open to receiving a pull request of?

Currently the exposure date is stored to UserDefaults, but looks like it's not used for anything. Even though Apple says "This property may report a date of relative precision, such as within one day of the actual event." maybe this date info could be fetched from UserDefaults on an jailbroken iPhone and then used to figure out who the infected person was?

Edit: Noticed that it's used for figuring the retention time. Could this still be a privacy issue?

We welcome contributions from the public. However there are some guidelines to follow:

1. We cannot accept new language versions and translations from community, this is because:
   • Some expressions used within the app are strictly coupled with Finnish law and thus must meet it's requirements
   • There's also a lot of domain specific terminology involved which must be handled by THL's board of experts
   • Small typo fixes can be processed manually but better way to report those is to raise an issue. We can then manually credit changes to issue's original author
2. Prior to committing to work, create an issue describing a problem, bug or enhancement you would to like to work on
3. Wait for discussion on the issue and how it should be solved
4. Wait for main contributors of the repository to handle the issue and clear it for implementation
5. Embrace the feedback and be patient. We are working as fast as we can to improve Koronavilkku and community's help is much appreciated

Please always add reference to related issue. You can bring up drop-down of suggested issues by typing #.

This pull request resolves # .

Also, remember to update CHANGELOG.md before merging your changes.

Modified app to use version 2 of the Exposure Notifications API.

• Instead of displaying the number of exposures, the app now displays the number of days for which new exposures have been detected.
• Only exposures newer than the latest currently known exposure are handled.
• The app is now responsible for displaying local notifications about exposures.
• Minimum supported iOS version increased to 13.7 / only v2 API is supported by the app.
• App badge displays the number of 'active' potential exposures (the same number as in the app UI).

Couple of notes:

• Plural support for text ItemDaysValue could be removed as unnecessary if the final swedish version doesn't need it either (pcs).
• The local notification is removed only if the user taps it or explicitly removes it, i.e. it isn't removed when app is opened e.g. via homescreen.
• Having 2 separate implementation of ExposureNotification protocol might seem a bit excessive now that only the latest exposure date needs to be known for the v2 case too. But I wanted to keep the v1 era data objects as-is (and not add any sort of type specifying field) so kept the 2 implementations after all.