Asana Desktop App Digital Signature Certificate is Expired

Briefly describe (1-2 sentences) the Bug you’re experiencing:
The digital signature that all the .exe files for the Asana Windows Desktop application expired on 1/27/2022. We use the signature to allow execution privileges’ so the app is now blocked from running since the sig is invalid.

Steps to reproduce:

Browser version:

Upload screenshots below:

Hi @Steven_Kaskinen, welcome to the Asana Community Forum :wave:

Thanks for flagging this. Could you please provide some screenshots illustrating the issue/error message you’re running into so that we can look into this further for you?

Looking forward to hearing back from you :slight_smile:

including pics of expired cert; it is both on all your exe’s after it is installed; as well as on your current 1.5.1 version setup file.

Thanks for following up, @Steven_Kaskinen. Could you please uninstall and reinstall the desktop app and let me know if this resolves the issue?

Looking forward to hearing back from you :slight_smile:

reinstalling does not help. The installer also has an expired signing certificate as well.

Without a valid certificate Windows flags the executable as untrusted as we required applications to be valid and signed to execute. This is a standard Windows security feature.

Your signing certificate needs to be updated and you’d need to push a newer version of the application and installer exe with the new cert.

Feel your frustration Steven - we ran into same issue on 28th of January and are waiting for Asana to publish a new desktop app with a non-expired certificate.

Perhaps alot of people only use the Web or non PC version which is why Asana are not themselves aware of the issue.

1 Like

Thanks for confirming, @Steven_Kaskinen and also reporting, @Russell_CK. Our Engineering team has confirmed that they are working on re-signing it with a new certificate and will upload a new version of the Windows desktop app once that is done.

I’ll keep you posted here!

Hi folks, good news! Our Engineering team have confirmed that was resolved with version 1.6.0, released on Feb 9. :tada:

This topic was automatically closed 16 days after the last reply. New replies are no longer allowed.