This is an unencrypted RBE file; it runs fine, but it doesn’t run after RBE encryption. Please help me, I’m a beginner.![]()
taistudio.rbz (82.5 KB)
This is an unencrypted RBE file; it runs fine, but it doesn’t run after RBE encryption. Please help me, I’m a beginner.![]()
taistudio.rbz (82.5 KB)
Please see this topic:
https://forums.sketchup.com/t/when-i-encode-using-rbe-my-file-doesnt-run/347271
This is the same as before:
EXTENSION_PATH = File.join(__dir__, EXTENSION_ID, 'main.rbe').freeze
Try removing the file extension, “.rbe”.
Don’t change or add “.rbe” to encrypt. The signing/encryption process does that to your .rb files for you.
So, use this:
EXTENSION_PATH = File.join(__dir__, EXTENSION_ID, 'main').freeze
The topic opener shared exactly the same file as a day ago punpun did.
It’s probably the same person, just with memory loss. ![]()
There must be some misunderstanding. It looks like there is some effort to ‘manually encrypt’ by changing file extensions.
Do extensions even work if you rename your files, .rbe?
plugin.zip (163.5 KB)
I checked your package and fixed the encryption/loading structure.
SketchUp is now able to reach the plugin files correctly after encryption.
next issue seems to be inside:
taistudio/tools/pline_cad/pline.rb
That file appears incomplete or corrupted in the package you shared, so the remaining issue no longer appears to be related to RBE encryption. Please send the last working unencrypted version of the plugin folder, especially this file, and I can check it again.
No, they will not. Extensions are just hints these days. The actual content of the file determines whether it is encrypted. Also, SketchUp’s encryption scheme is proprietary, so nobody else can generate a correct extension rbz without illegally cracking the encryption system.
That’s what I suspected about the just appending rbe. It seems like that is what the OP is doing, so I would’ve guessed it would not have run at all. The OP seems to say otherwise.
As far as having the .rb in the require statement when encrypting an extension that was working fine… been there, done that!