Cannot Sign the .rbz file due to: Total size: NaN undefined or Total size: 0B

Developers Extension Warehouse for Developers
1

Issue

We are having an issue with signing our rbz files for Veras. We have not changed anything about our process, but we are getting a new error on the Extension Warehouse signing page. See imaged below for the different errors.

image
image1259×823 24.7 KB

image
image1259×823 24.9 KB

Last Time it Worked

This process last worked on Nov 5th with the Veras 1.9.7.1 release. However, we cannot get it to work.

What we tried

  • checked that the file size is actually not zero, and that the archive has the correct content:
    image
  • tried to use WinRar & windows zip to create the rbz
  • tried different dev machines
  • tried the original code branch that had no issues, and it still didn’t work
  • tried different browsers: chrome, edge, opera, firefox
  • checked this post: Trouble Signing RBZ

Help

I attached a sample rbz file that doesn’t contain the source code below. This file also fails, and it’s built with the same process. The file can be used for testing.

Veras_SketchUp_Extension_Archive_Empty.rbz (542 Bytes)

It would be great if anyone else has more insight into how to resolve this, as it’s disrupting the release pipeline. Thank you for support!

2

We also tried 7-zip with all the compression methods:

image
image626×573 21 KB

Still, no success.

3

This is odd! I just tried to sign the sample file attached above on my Android phone, and it worked!

Screenshot_20241220-210706
Screenshot_20241220-2107061440×3120 151 KB

4

We had many issues signing our files in the past, but at the moment we dont encounter issues. In the past the issues were related to a buggy signing process, to many files in the RBZ or to large of an RBZ. Very often less files in the RBZ or removing all image files would fix the issue for us, though not always.

1 Like
5

@PeeWee - that makes sense. However, the test file above is as small as you can get. It’s only the one ruby file and an empty folder.

Anyways - tried this again, and instead of drag and drop, I clicked the Browse button to select a file, and surprisingly IT WORKED!!

So it seems like the drag and drop behavior is broken. As soon as you use the browse button it works.

For us, this is now resolved, as we can move forwards with building the app. However, others might come across the same issue, if they are using the drag/drop file for signing extensions.