I am trying to add auto update support to my electrom-app using electron-updater(electron-builder version), and it has gotten to the point where it starts to download the update but the download progress just decreases and increases infinitely afterwards. After checking the logs, it says there is a sha512 checksum mismatch, and that it got an incorrect SHA512 value. I tried to solve it by checking some previous issues and trying applying those but they didn't work. I read that it might be because of my code signing techniques(I use my EV Code signing cert to code sign my app after I make the executable using a sign tool command). To try and solve this, I tried integrating it with electron builder using sign.js, but that did not work, since it would try to sign the .exe before it even existed. Additionally, I tried going into the latest.yml and manually changing the sha512 values of the update and the original software to match, but that didn't make a difference either. What can I do, and what exactly does this error mean?
Here is info about my project if that helps.
Error Code
Error in auto-updater. Error: sha512 checksum mismatch, expected <long_encrypted_value>, got <different_long_encrypted_value>
Electron-Builder Version: 22.9.1
Node Version: 16.7
Electron Version: 18.2.0
Electron Type (current, beta, nightly): Current
Electron Builder Version: 4.3.9
Target: Windows
Related
I am building a menu bar app witih rumps and using py2app to export. When I am building using Alias mode its completely fine.
When I am building for production however it prompts me this error:
ValueError: New Mach-O header is too large to relocate in '/Users/isaacng/Developer/Menu Bar Spotify/Rumpify/dist/rumpify.app/Contents/Resources/lib/python3.10/lib-dynload/cryptography/hazmat/bindings/_rust.so' (new size=2264, max size=2260, delta=72)
I have tried rolling back a few versions of py2app and nothing. I found this FAQ in py2app but I really don't understand how to rebuild binaries with enough space?
https://py2app.readthedocs.io/en/latest/faq.html
This error can be avoided by rebuilding binaries with enough space in the Mach-O headers, either by using the linker flag “-headerpad_max_install_names” or by installing shared libraries in a deeply nested location (the path for the install root needs to be at least 30 characters long).
Very greatful if anyone can figure this out! I really don't want to use pyInstaller!!
I've got a very curious error to share regarding Xcode localization process. I will try to share as much detail as legally possible.
From Xcode, I am trying to export an XLIFF file to send to our translators, via "Editor > Export for Localizations". However, this immediately throws error with the message:
The operation couldn't be completed. Argument list too long
This is indeed confusing, as I cannot find a more verbose log anywhere (I have already tried checking my Console.app). So, I spent quite a few time googling – to no avail. I couldn't find similar case like this. The error itself happens only when I am trying to export for localization. I can build and run the app just fine.
Facts
~ $ xcodebuild -version
Xcode 8.2
Build version 8C38
~ $ xcode-select -version
xcode-select version 2347.
~ $ echo $PATH
/Users/david.christiandy/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/david.christiandy/arctools/arcanist/bin:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands
I am using Xcode 8.2 on macOS Sierra 10.12.5.
The error happens only when I try exporting from localization. This is also true when I run the localization process via xcodebuild -exportLocalizations.
I can build and run the app just fine. (I believe) there's no problem with my header search paths.
Attempts
Thought there was something wrong in the code, so I tried to run the export process (via xcodebuild command) in a CI. Somehow, it's working. For the record, I am using Bitrise CI with the same stack as my system (Xcode 8.2.x, macOS 10.12)
Asked colleagues to run export process on their machines, and they have the same error.
This leads me to think that there must be something wrong with the configuration. So I made a standalone project to confirm that the export process fails consistently. Turns out, it works just fine!
So, the hypothesis I got currently is:
There's probably something wrong in the code, and
There might be tools/software (that most of our iOS engineers installed) that might contribute to the error (since the CI completes just fine).
I don't know why the CI can run the export process just fine, and I don't know when it might suddenly stop functioning (just like our local machines).
Appreciate any help on this matter. Thank you!
I also asked this question on Apple developer forums, here is the link: https://forums.developer.apple.com/thread/86762
“Argument list too long” sounds like E2BIG, which you get when you try to run a child process with a huge argument list (I believe the current limit is 256 KiB). I suspect that Export for Localizations is running some sort of command line tool to do that work (probably the extractLocStrings tool, which you’ll find lurking within Xcode’s app bundle) and passing it full paths to each of the files in your project. Depending on how many files you have and how long those paths are, it’s easy to run into problems like this.
One of the ‘fun’ things about bugs like this is that they are dependent on where you place your project. Things might work if the project is at the top of your home directory but fail if it’s nested deep inside a subdirectory.
That also suggests a potential workaround, namely, to move your project further up in the directory hierarchy.
Finally, you should definitely file a bug about this. I believe we’ve seen this before (r. 30703294) but your report will help reinforce that this is causing problems for developers in the field. Please post your bug number, just for the record.
Several days ago before I read this answer, I managed to get the export working by deleting some folders via Xcode (remove references only). Initially I suspected that there's an invalid format within the folders that I deleted, but when I tried deleting other folders, the export process works just fine.
I also tried exporting strings using Xcode 9, and I didn't encounter the problem. So hopefully this bug is only for Xcode 8.3.3 and below.
I am little concerned about how people treat the following issue.
Basically it sounds like "Build fails on Jenkins with the ResourceRules.plist: cannot read resources"
My circumstances are:
1) Jenkins
2) Locally I work in Xcode 7 beta (on a separate branch)
3) My teammates work in 6.4.1 and for them everything works fine
4) Jenkins slave has Xcode 6.4.1 installed
Some of you will say "this question was asked millions of times", like here, here, here, here.
But the documentation says the following:
Resource Rules
Systems before OS X Mavericks v10.9 documented a signing feature (--resource-rules) to control which files in a bundle should be sealed by a code signature. This feature has been obsoleted for Mavericks. Code signatures made in Mavericks and later always seal all files in a bundle; there is no need to specify this explicitly any more. This also means that the Code Signing Resource Rules Path build setting in Xcode should no longer be used and should be left blank.
So my question is why everybody is so quick on hand to bypass, hack, workaround this issue, when the documentation clearly says that is should be blank and it's obsolete?
What is the real problem behind this? Why the build fails on something that is not required for several years?
I had the same problem. The solution suggested by Mr.Dan Cutting here works for me.
Just to save some time, here is what we need from the web link.
"As of Mavericks, the resource-rules option should not be included when signing apps, but for some reason the script still passes this option along to the code signing tool.
The workaround is to alter the PackageApplication script so it no longer does this (which will require sudo access). Line 155 of the script constructs the parameters to pass through to the code signer, so we can simply remove the references to resource-rules:"
//Remove - Begin
- my #codesign_args = ("/usr/bin/codesign", "--force", "--preserve-metadata=identifier,entitlements,resource-rules",
- "--sign", $opt{sign},
- "--resource-rules=$destApp/ResourceRules.plist");
//Remove - End
//Add - Begin
+ my #codesign_args = ("/usr/bin/codesign", "--force", "--preserve-metadata=identifier,entitlements",
+ "--sign", $opt{sign});
//Add - Starts
If you have used Xcode version greater 6.1 then change the below line
$(SDKROOT)/ResourceRules.plist
TO
CODE_SIGN_RESOURCE_RULES_PATH=$(SDKROOT)/ResourceRules.plist
I have used EmguCV Dll and OpenCV Dll to trigger(switch on) my camera when a button is pressed. The application works fine while building and compiling. After building the setup file,the application.exe file works fine in my system.In any other system the application works fine till the Camera is triggered, the moment camera is triggered, the application crashes . First I thought maybe the issue is with 32 bit and 64 bit. I built two separate setup files specific for 64 bit and 32 bit and still the application crashes while triggering the camera. I also read that Microsoft C++ Redistribute Package has to be installed and I tried installing that, Still the application failed and did not trigger the camera. Kindly help regarding this issue
These are my logs :-
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: aindrasmartattendance.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 5523aef5
Problem Signature 04: Emgu.CV
Problem Signature 05: 2.4.10.1939
Problem Signature 06: 548278fa
Problem Signature 07: 3ac
Problem Signature 08: 14
Problem Signature 09: System.TypeInitialization
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 16393
Additional Information 1: dac2
Additional Information 2: dac2dba5ddc5d0577434255af55618b7
Additional Information 3: f0bd
Additional Information 4: f0bd2045bac4d1dc98365de98e6112a2
Thanks!
I'm trying to sign our BlackBerry app, but now it's asking for "RIMAPPSA2" signing key, which is the signing key for private APIs (which isn't allowed in the app world I assume). So I want to remove this requirement so I can actually run the app on devices.
There's nothing in the build log. My app does NOT use any of the following packages (which the internet suggests might be the issue):
net.rim.vm.Persistable
net.rim.vm.*
net.rim.device.api.browser.field2.*
net.rim.device.api.browser.field2.debug.*
net.rim.device.api.script.*
org.w3c.dom.jsp2.* <- actually is uses org.w3c.dom.*, but I've had an app not require this that already had this package in it.
net.rim.device.api.io.Seekable
And I'm not importing any external JARs (although I was before). I'm using the 4.5 JDE.
How can I find out what is making the signer tool require this signature?
Is there any way to track down what is causing this signature (RIMAPPSA2) to be required?
This might be due to a bug in Eclipse or RIM. You might not be using the RIMAPPSA2 classes.
OK, so its hard to believe but this page might fix the problem for some:
Frustrations with Blackberry Developer plugins for Eclipse
Basically its a bug, and by changing the Application Descriptor, saving, removing & re-adding the JAR file, the problem is fixed.
Follow-up #1 - might not work:
The above solution enabled me to build & sign the app. Unfortunately the app won't run on the phone Module 'MyApp" attempts to access a secure API.
Follow-up #2 - this worked for me:
I documented a full solution that worked for me here:
BlackBerry - use own JAR file in own project
In my case, I was importing my own JAR file, and I needed to set that project's build type to be a MIDLET. Setting it as LIBRARY or APPLICATION caused problems.
I've not tried it, as I am waiting for my signing key.
If you use eclipse, you can have following settings that can be turned off.