0

We have a windows app that runs on Windows 8.1. We use a test certificate with sideloading to install the app. The key is expiring in a few days and we are in the process of generating a new one and deploying it. Meanwhile, I would like to know will the app stop working after the certificate expires? I tried to post date my device and test the app which worked even with a expired certificate. Is that the intended behaviour? I do understand for any future deployment of the app it does need a renewed certificate, but will the current version continue to work even after the certificate expired.

I tried googling and go through various articles but could not find a relevant answer.

XtremeBytes
  • 1,469
  • 8
  • 12
  • Please choose the appropriate tags, uwp and windows phone 8.1 may not be suitable if you mean app runs on windows 8.1. – kennyzx Nov 07 '17 at 03:04

2 Answers2

0

The current installed version will cease to work after the cert expires. At app start up, a checking is performed on the cert that is used to sign the app, if the cert has already expired, the app can not open. The symptom is the app window is showing for a second then immediately minimized.

In your test, make sure the app is terminated (in Task Manager) before setting system time so that you won’t end up testing a app resuming scenario. And you need to disconnect from corporate network since the system time can be synchronized with corporate servers. Then try to reopen the app and you should be able to observe the symptom.

Update:

I realize I was following some particular steps in my test, I first installed a package, then right before launching it for the first time, I set system time, and then launched the app. In this way, the app failed to open. The error looks like

App failed with error: Element not found.

I guess some extra deployment step which takes place in the first launch is blocked because the cert has expired. So the app cannot be activated.

If the deployed app has run at least once, looks like it can continue to work without any issue after the expiry date.

kennyzx
  • 12,845
  • 6
  • 39
  • 83
  • Thanks very much for the response. I ran the test scenario's you mentioned and the app worked fine without any issue. Terminated and restarted the app, restarted device etc.. and in all instance it is ignoring the expired certificate. Ours is windows 8.1 app and not a windows phone app. Not sure if the would react differently. Is there a package settings that enforce or ignore the certificate check at app lauch? – XtremeBytes Nov 07 '17 at 18:17
  • Some update. I think there is no problem for installed app continue to work. The steps I mentioned are actually a test case performed by my team, looks like we need to update the test case according to this new finding. :) – kennyzx Nov 08 '17 at 03:09
0

Recently we faced the same issue in our windows 8.1 app. The Current installed Build works normal even after the certificate expired. But the new build will not get installed as it will look for valid certificate.

Incase if you are in need to install build with expired certificate you can change the date(date before certificate expiry) and you can install the same build. After successful installation you can change the date and run the app.

Mohanvel V
  • 768
  • 4
  • 17