SOLVED: Regenerating key signatures does not regenerate code elements in components

Bugs
1

When regenerating key signatures, code elements specifically within a components show as invalid in the builder, and have to be manually signed by going into the component and signing the code. The code also does not appear in the Code review section in the Settings.

EDIT: To add, usually the “Sign Code” tag is red, indicating the code is not signed. However, the tag is white, which usually indicates the tag is signed.

2

Hi @HyperHunter,

can you show me the steps to reproduce this? I created a component (block), with the code element inside.

  • In the builder, it will show me that it’s not signed - it will be red
  • If I check the settings, I will also see it, and that the signature is invalid. If I sign it, then it will say that the signature is valid.

CleanShot 2025-05-29 at 08.18.08@2x
CleanShot 2025-05-29 at 08.18.08@2x1310Ă—802 40.5 KB

Is there something that I’m missing? Could you record a step by steps video, on how to replicate this issue?

Thank you,
Matej

3

Hey @HyperHunter,

II just now saw that you are using the 1.12.4 version - I was assuming that you use 2.0-beta. Can you try with 2.0-beta version (on the staging website), and let us know. I believe it should be fixed there.

Thanks,
Matej

4

This issue is fixed in Bricks 2.0 Alpha

EDIT: I didn’t realize you said Beta and not Alpha, I tried this on an Alpha build of Bricks 2.0 and it seems to be resolved in Alpha

1 Like
5

Perfect, then I’ll mark this topic as solved. And yeah, alpha should solve this issue, I just mentioned beta because it’s the latest one :slight_smile:

Thanks for confirming.
Matej