Using the 112nl app does not work

Sparks

Hi, from the sandboxed Play Store I installed the 112nl app, the official app of Dutch emergency services (police, ambulance and fire brigade) for making an emergency call, very suitable for deaf and hard of hearing people like me. The installation went smooth. However, registering my mobile phone number results in the following error:

Error returned from API code 403 body App attestation failed

I tried several methods described in https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos, nothing works. Is it related to the Play Integrity API? If yes, I'll try to contact the developer.

other8026

Sparks Is it related to the Play Integrity API? If yes, I'll try to contact the developer.

This sounds likely. Or have you removed Google Play Store or Google Play Services' network permission? If you have, try enabling the network permission again. If not, your best bet is to contact the developer.

fid02

Sparks I tried several methods described in https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos, nothing works.

I can reproduce.

Sparks

Thanks for thinking with me. I have since sent an email to the developer. Let's hope the civil service mill (112nl app is a government owned app) is not running very slowly. I'll keep you posted here.

Michiel

It may also be related to the governmental network issues that occurred today: https://nos.nl/artikel/2534851-systemen-bij-overheidsdiensten-plat-door-storing-bij-ministerie-van-defensie

fid02

Michiel Are the network issues supposed to be resolved now? Because the app is still showing me the same error on GrapheneOS during phone number registration, yet it is working fine on stock PixelOS (I didn't try doing an actual emergency call of course, but I can register my phone number fine and can get to the main menu of the app).

Michiel

fid02 I think everything should be up and running by now. I had same error message with my spare Huawei phone with an unlocked bootloader (my Pixel is being repaired so I cannot check). So it looks like an attestation issue.

Sparks

It has nothing to do with the network error as fid02 already has found out. Few months ago I faced the error. I wasn't aware that it could be related with the attestation issue and was waiting until the error might be resolved. But unfortunately, no. As mentioned here, two days ago I wrote an email to the owner of the 112nl app. Now I'm waiting for the reply.

fid02

@Sparks
In case you're not aware, GrapheneOS has an attestation guide which will enable developers to support GrapheneOS without having to remove the integrity checks for other OSs altogether. Might be worth forwarding it to 112nl just to make then aware of the option. https://grapheneos.org/articles/attestation-compatibility-guide

Sparks

Yes, I know that guide, I forwarded it already to 112nl :-). By the way, I have just received a reply. However, the response is clearly drafted using a script. I got the tips such as "please remove the first zero in the phone number", and "try it with and without wifi". It seems that the person is not technically skilled. I replied in a simple language that the problem is related with the attestation compatibility and insisted that the problem should be dealt with by developers of the app (in a very friendly way, of course). Now again waiting for the useful solution.

fid02

Sparks Sounds like first-line support. If they receive a reply that what they are suggesting has been tried without success (even though it really is useless troubleshooting), I think they are more likely to forward it to second line of support, or further up the system, without any more back and forth. At least that is my experience from dealing in customer support.