Do I need to sign my .app file everytime I make a change?

(0) Share

Report

Posted on by jdrco

479

I was able to get my .app file signed, but I am noticing that when I make a change to my AL extension, the .app file gets replaced by a new .app file without the digital signature.

I am wondering if resigning the .app every time is the standard or if there is another method of keep the .app file signed?

All responses (4)

Answers (0)

jdrco 479 on at

Like (1)

Report

RE: Do I need to sign my .app file everytime I make a change?

Thank you again.
Suggested answer

Inge M. Bruvik 999 Moderator on at

Like (1)

Report

RE: Do I need to sign my .app file everytime I make a change?

If you use f.ex. Azure Devops or Github you can build build / release pipelines that automates the process for you.

You can find alot about this CI/CD approach f.ex. on freddys blog.

freddysblog.com/.../

There are also some add-ons avalible for Azure Devops that can help you automate your build process.

You will find info about that solution on f.ex waldos blog.

www.waldo.be/.../

Hope this helps you further.
jdrco 479 on at

Like (0)

Report

RE: Do I need to sign my .app file everytime I make a change?

"AppSource will also require you to change the version no. for every change you make."

Is there a way to automate this every time I build?
Suggested answer

Inge M. Bruvik 999 Moderator on at

Like (0)

Report

RE: Do I need to sign my .app file everytime I make a change?

You have to sign the app. file every time you produce a new build.

The signing is there to prove that the file have not been changed after it was signed

AppSource will also require you to change the version no. for every change you make.

So every time you change something and build the app file you will have to sign it again.