This seems to be a fairly common problem...a possible solution I found:

If your (probably Android) device is saying "checking exposure keys" and stuck indefinitely, it seems the fix is either you to turn Bluetooth Tracing on in NZ COVID Tracer, or turn off Exposure Notifications in the Android system settings depending on your preference.

cshwone:

 

Not seeing any of the above behaviours on my Samsung A50. App just sits there, BT enabled with no impact on my use of the phone or notifications coming up.

 

No issues on my Xiaomi Note 7 either. My phone has had little use all day (just Google maps navigation the 40mins to work and 40mins back home as well as the occasional WhatsApp/Facebook messages) and it's now sitting on 83% battery (fully charged when I left home around 7ish). Battery usage stats shows 1.62% to Bluetooth and 0.51% to COVID-19 app--with the vast majority going to Google Maps as expected.

Interesting...

https://github.com/minhealthnz/nzcovidtracer-app 

mkissin:

turn off Exposure Notifications in the Android system settings depending on your preference.

Not seeing these behaviours, touch wood.  Galaxy S8, BT enabled.

Oblivian:

 

The keys, per Googles implementation of it... changes every ~hour for the broadcaster. And does a server exposed keys check at least once a day.

 

But it seems mostly samsungs that are displaying this. And either toggling the system built in control and letting the app re-enable it may work. (or vice versa) Or force updating the Playstore framework. It's still not clear which is the cause. It's as if one is trying to toggle it on, while it already was. As it's the sort of message that appears as you set it up within the app and it does the various probes

 

Checking internet

 

Checking device compatability 

 

And so on.

 

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

That's the default delivery method for CEN so quite possibly.

https://support.google.com/googleplay/answer/9888358 

Most Samsung users online found that it didn't auto update to the latest version. either clearing it's data for it to reload fully or going into the about and making it for check seems to

May also be why the toggle switch fixes, the initial deployment might have a conflict with the toggle on switch within the app

Technofreak:

 

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

 

In this case I think it's better to report to the MoH following the links I've posted before and perhaps suggest they check if it's a Google Android or not.

Technofreak:

 

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

 

Anyone who is running a rooted or custom built Android phone should ALWAYS assume that apps AREN'T going to work. You would have had to side load it from the Play Store anyway as it isn't like they publish the APK.

The assumption any app will work is fundamentally wrong, and should not be the responsibility of MoH to fix your problem.

Use a stock firmware using a fairly new version of Android and it will work fine.

BarTender:

 

Technofreak:

 

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

 

 

Anyone who is running a rooted or custom built Android phone should ALWAYS assume that apps AREN'T going to work. You would have had to side load it from the Play Store anyway as it isn't like they publish the APK.

 

The assumption any app will work is fundamentally wrong, and should not be the responsibility of MoH to fix your problem.

 

Use a stock firmware using a fairly new version of Android and it will work fine.

 

You keep banging on about using a stock Android OS. I don't use an Android OS of any sort so there is no point in telling me to run a fairly new version of the stock firmware. Sailfish, the OS I use, can run an Android compatibility layer and any Android apps that don't require GApps run perfectly well. Even some that require GApps still work with one or two features missing.

I don't expect all the functionality to work. I never said that and I don't expect for one moment for the MOH to fix it. I was merely passing on my experience. In this case it would appear even stock Android phones are experiencing this problem. Someone involved with the Contact Tracer app has been in touch with me as it appears the may be an issue with the EN plug in.

freitasm:

 

Technofreak:

 

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

 

 

In this case I think it's better to report to the MoH following the links I've posted before and perhaps suggest they check if it's a Google Android or not.

 

One of the app developers made contact with me today.

BarTender:

Technofreak:

I suspect the problem for me is I don't have Playstore or GApps on my device so any functionality requiring that is going to fail. This probably explains why it just sits there checking exposure keys.

Anyone who is running a rooted or custom built Android phone should ALWAYS assume that apps AREN'T going to work. You would have had to side load it from the Play Store anyway as it isn't like they publish the APK.

The assumption any app will work is fundamentally wrong, and should not be the responsibility of MoH to fix your problem.

Use a stock firmware using a fairly new version of Android and it will work fine.

@MadEngineer, there's also an iOS update in the last 24 hours to install.