I upgraded electron to 9.4.0 and electron-buiilder to 22.9.1 in Mac Big Sur.
I used the autoUpdater and dialog from electron to show successful or failed message.
However, it kept saying code signature at URL did not pass validation.
When I built the OS version, the signing phase is passed. Also, I tried to codesign -dvvvv --extract-certificates to see the hash information and is the same with the workable one.
I am wondering if the new version of mac caused this issue?
const {autoUpdater, dialog} = require("electron");
dialog.showMessageBox(dialogOpts);
Related
Problem summary : I would like to submit an app to the Apple App store (TestFlight). I am using Transporter v1.1 to submit the app. I am getting the following error in Transporter during the submission process. Please note that I am not using Xcode in this process.
Actual result:
ERROR ITMS-90596: "Invalid Bundle. The asset catalog at 'Payload/ExpoKitApp.app/GoogleMaps.bundle/GMSCoreResources.bundle/Assets.car' can't be processed. Rebuild your app, and all included extensions and frameworks, with the latest GM version of Xcode and resubmit."
Expected result : successful submission to the app store.
Development environment : Expo 36.0.0 / macOS High Sierra v 10.13.6 / Processor 2,3 GHz Intel Core i5 / Transporter v 1.1
What have I tried ? :
Deleting all node modules and installing them again (npm install).
Deleting any old Xcode folders on my mac. Please note that I am not using Xcode.
Checked the version of xcode in package-lock.json. It is 2.0.0 but it is being used as dependancy and not as a direct tool in the submission process.
Generate a new build thrice and submitting it once more in Transporter.
Can anyone please help me in this process ? I know this question has been asked before but the case is not applicable to me because I am not using xcode or application loader to submit the app.
This could help someone in a similar situation. Here is how I solved my problem with the advice of a senior developer.
Using expo diagnostics I found out the version of Xcode that my expo toolkit was using. The answer was undefined because I wasn't using Xcode at all.
Being on macOS High Sierra 10.13.6, I needed Xcode 10.1 for compatibility.
I downloaded Xcode 10.1 and also the compatible command line tools.
I transferred the installed Xcode from the downloads folder to applications folder.
Again ran expo diagnostics and noted that expo has taken into account the associated Xcode version.
Ran expo build:ios
Downloaded the .ipa file generated by expo on their server.
Submitted the .ipa file using Transporter to the Apple app store (TestFlight).
Successful submission.
I'll try to be as concise as possible but feel free to ask for further details.
First of all, on both machines code signing passes and there are no errors at any point in Xcode. When archiving app and exporting ipa on my MacBookPro the app successfully installs and runs on a device. When doing the same on our CI server (manually via Aqua session, not through a script) the app installs but crashes as soon as the app references any library with the following error: kernel(AppleMobileFileIntegrity)[0] <Error>: Library Validation failed: Rejecting '' (Team ID: , platform: ) for process '(<decode failure invalid size>)' (Team ID: <private>, platform: <missing data>), reason: <missing data>.
The only difference between server and my Mac configuration is that server runs on El Capitan and I've updated to Sierra.
Configuration:
Cocoapods v. 1.1.1
XCode v. 8.1 (8B62)
Provisioning profile permission: Enterprise distribution
OS versions are in discrepancy (read above)
I've searched a couple of days for the solution and didn't find anyone having the same problem, let alone solution for it. I've probably tried all that you are going to suggest, but I'm still hoping someone has a solution to propose without updating server to Sierra.
I have just updated my OSX to Yosemite, then I ran into an error when submitting a new build to TestFlight with the TestFlight desktop app.
error: /usr/bin/codesign --force
--preserve-metadata=identifier,entitlements,resource-rules --sign 2c30db522ceda29332f9f85951addff0276e0de1
--resource-rules=/tmp/sesLW20J9I/Payload/MyApp.app/ResourceRules.plist /tmp/sesLW20J9I/Payload/MyApp.app failed with error 1. Output:
Warning: usage of --preserve-metadata with option "resource-rules"
(deprecated in Mac OS X >= 10.10)! Warning: --resource-rules has been
deprecated in Mac OS X >= 10.10!
/tmp/sesLW20J9I/Payload/MyApp.app/ResourceRules.plist: cannot read
resources
Anyone has got an idea?
OK, finally I find a solution to this issue. It seems that the resource rules file is not generated by default in XCode 6.1.
To generate the resource rules file as before, go to project setting, search for
Code Signing Resource Rules Path, and set its value as
$(SDKROOT)/ResourceRules.plist
After this change, rebuild your target, TestFlight desktop app will work as before.
The app has not been updated to work on Yosemite (and I doubt it ever will because it was developed before Apple acquired TestFlight iirc and Apple has integrated the uploading process into Xcode.
I am stucked while uploading to app store, with the message "Your application is being uploaded..."
I have tried all the steps mentioned here:Xcode stuck at “Your application is being uploaded”
Things I did,
My firewall protection is off
Changed #https.proxyPort=443 proxy port to https.proxyPort=80 in net.properties.
Tried to upload from Application Loader but stucked at "Authenticating with the iTunes store..."
Deleted old certificate,and provisioning profiles, Got new ones.
None of them are working. My system configuration are as follows: OS : 10.9.2 Xcode :5.0 Java : I upgraded from jdk 6 to jdk 7
Jdk folders at Jdk Folders at /System/Library/Java/JavaVirtualMachines/ and /Library/Java/JavaVirtualMachines are -1.6.0.jdk and -jdk1.7.0_25.jdk ( I have tried with 1.6 alone and 1.7 alone also).
When I run java -version from terminal - java version 1.7.0_25
( I have also tried with version 1.6)
JRE version: From system preferences - > Java -1.7
I have tried to upload from two different places but still no luck.
Are there any other methods to solve this issue? Or is my system configurations, java version ,JRE etc wrong,should i update Xcode?
This is my first upload to app store after upgrading to mavericks/Xcode 5. Prior to this there was no problem. When I validated the app before distributing, it is validated without any problem.
Any help is greatly appreciated.
It happens to me also many times, you can do Something like,
if upload from Application Loader Make sure you are login into itunesconnect in safari.
Uplaod it to some older Version of Application Loader
Upload from Different MAC may some of your friend or colleagues.
I'm using phonegap build service for our iOS application, (the app is built on HTML5), and the delivered ipa file from phonegap works fine using a development provisioning profile on our devices. However, when attempting to load the app to the app store (using a release provisioning profile for itunes), we get this from the application loader
ERROR ITMS-9000: "Unsupported Architectures. Your executable contains
unsupported architectures '[12-11]'." at SoftwareAssets/SoftwareAsset
(MZItmspSoftwareAssetPackage)
This happens for versions 2.8 and 2.9 of Application loader. We're using Phonegap build service 2.7, 2.9 and 3.0. How can we determine what the "unsupported architectures" are from PhonegapBuild ? is there a method for identifying what features we are using that may be contributing to this error ?
I have managed to successfully upload the app. The issues was that I was running OSX 10.7.5 and running Application Loader 2.8 (AL), which seems to be compatible with Moutain Lion (10.8). Once upgrading to Mountain Lion you can do another update to 10.8.5 which will install Application Loader 2.9. (You can upgrade to 10.8 via the Apple=>"App Store" option on your Mac. It is a paid upgrade.)
If you downloaded the latest AL from the itunes connect portal and install it, it doesn't tell you that it's incompatible with older verions of Mac OSX before 10.8. All you'll get is an obscure message that your ipa is an "unsupported architecture" which in "Appleonean" means "You need to upgrade your version of OSX". Extremely misleading as it's nothing to do with your IPA, it's your OS. Even reading the PDF from Apple about AL there is no indication for minimum system requirements..
same here - this app previously uploaded fine but when I try a support update I get this error along with a warning about a missing icon of 120px, 76px, and 152px