Auditor app crashes on initial device pairing

[Jawshy]

The Auditor app keeps stopping when attempting to perform the initial pairing between a phone and tablet.

Auditor: Google Pixel 3a XL [Model: G020B]
Auditee: Galaxy Tab A 10.1 2019 (Wi-Fi) [Model: SM-T510]

Both devices are running Auditor version 17.

Steps to reproduce issue:

1. Launch Auditor on both devices.
2. Tap 'auditor (device performing verification)' on the Pixel.
3. Tap 'auditee (device being verified)' on the Tab A.
4. Scan QR code shown on the other device.
5. The app crashes.

No issues when auditor and auditee are switched; pairing and verification are successful.

Please let me know if additional information is needed.

[thestinger]

Can you trigger the crash and then go into developer options and use the take bug report feature to send a bug report to contact@attestation.app? Note that the bug report zips may contain some sensitive data if crash dumps or logs contain it.

Alternatively, you could use ADB to run adb logcat on an attached + whitelisted host computer and then trigger the crash.

It's likely that a minor mistake was made in the metadata added to support this tablet which will need to be corrected.

[Jawshy]

Sent 📬

[thestinger]

@Jawshy Can you check if this is still a problem and send another bug report?

[Jawshy]

The app still crashes on the tablet. I've sent a bug report to contact@attestation.app

[thestinger]

@Jawshy I think ce8c0f4 will fix the issue. I can make a test release for you to try on the Auditee.

[thestinger]

It might be better to just make a normal release due to how Auditor releases impact attestation.

[thestinger]

Adjusted this to a0cc37c to avoid weakening the check on other devices.

[thestinger]

This will be fixed by the next release when I finally find the time to put that together...

[thestinger]

@Jawshy This is FINALLY released in version 18. Sorry it took so long.

[Jawshy]

I updated Auditor to version 18 on both devices and tried verifying the tablet again. The app didn't crash, but the verification failed on the first attempt. Upon clearing the auditee parings, the initial pairing was successful on the second attempt. Cheers.

[thestinger]

It probably failed due to the previous failed pairing. If the pairing is incomplete, the device being audited doesn't actually know that.