The client.wyc files include the public signing key. If you don't include an updated version of that, then any update can be installed.
I'm trying to understand how to verify that signing the updates is working.
I started a project with signing off, and then in a later version, I turned signing on. After doing this, I was able to install and update for my app successfully, when I expected to get a invalid signature error.I then changed the signing key in the project and created new version. This also updated successfully, when I expected it to not be able to update. Is this expected behavior, or can you tell me why I'm seeing this behavior? I'm not manually changing any files from my client install between updates.
Thanks
The client.wyc files include the public signing key. If you don't include an updated version of that, then any update can be installed.
Thanks, I was including the client.wyc, but I didn't realize that a new one wasn't being generated each time from my script.
Is there a way to regenerate that file from the commandline, or do you need to regenerate it from within the WyBuild app?
I'm still not able to see an update fail to install.With a signing key, I generated a new client.wyc file and included it in an update.After applying that update, I verified that the client had that updated file.I then changed the signing key in the project, and generated a new update.That second update with the new signing key still installed without issue. Why is that the case?
Thanks
Rebuild wyUpdate.
Include the client.wyc in your app.
All subsequent updates will return signing.