I want to create a electron build for Mac Mini M1 support but the build process taking so much of time to generate a webpack build.It takes around 5-6 hours and still showing me only 14%
Can anyone help out from this issue.I have attached a screen shot below.
There is a python issue. Try to install python version 3.8 or greater and nodeJS version 14.15.3 or greater.
Compile your custom addons again with using electron-rebuild command like this
electron-rebuild --arch=arm64
Then create a build it will definitely working.
Related
i am new to Electron so I went through all the guick start guides, examples and tutorials. I have build a simple Website that i need to convert with Electron and publish as a Windows exe file.
As i am working on MacOS, builds for MacOS are running, all fine.
For Windows i´ve installed mono and wine and found a great tutorial here
When using electron-packager with the following command, it generates an exe which runs only on Windows 10 - but not Windows 11. There is no error message, just nothing opens.
"npx electron-packager . <appname> --platform=darwin,linux,win32 --arch=ia32,x64 --icon=path/to/icons/dir"
When using electron-builder with the following command, it generates an exe which runs only on Windows 11 - but not Windows 10. There is no error message, just nothing opens.
electron-builder -mwl
Can anybody help me out, what´s the right command/parameter to generate one .exe for both platforms? Cannot find a solution on my own after 3-4 hours search, trial & error.
Thanks in advance.
I'm using the open source Titanium CLI for updating an app that's currently in the Apple app store. It builds and runs in the simulator without any problems using the command
ti build -p ios
When I try to build for the app store I use the command
ti build -p ios -T dist-appstore -R <company> -P <distribution certificate>
and get an error message
[ERROR] titanium_prep failed to run (10)
[ERROR] This application cannot be built with the Titanium open source SDK because it is an Appcelerator Platform registered application. Please use the Appcelerator Platform CLI tools or Appcelerator Studio to build this application.
I've unregistered the application with the Appcelerator Platform, but it hasn't corrected the problem.
I'm using Titanium Command-Line Interface, CLI version 5.0.6, Titanium SDK version 6.0.0.v20160131225447 and Node version 0.12.7.
Any help resolving this would be greatly appreciated.
There is a migration guide at https://github.com/m1ga/from_zero_to_app/blob/master/appc_to_ti.md
It seems you need to use a GUID that is not registered with appcelerator in the tiapp.xml.
It's also worth removing any <appc-...> or <property name="appc-..."> references to appcelerator services that will be turned off, and set <analytics>false</analytics>
I'm on a Mac with node 0.12 and I was having the same issue with Titanium SDK 5.X.X, but I have changed it to 4.X.X and now I can compile without errors.
I hope you don't need Titanium SDK 5.X.X. or 6.X.X to make your code run...
I met the same problem.
Solution:
re-create your app using $ ti create
or, just build this app using $appc ti build ...
Long explanation:
Our experience is: don't create ti app using $ appc create, just use $ ti create ...
in China mainland, the appc command is not usable at all because of GFW.
I found the related file is the titanium_prep file, which is binary, I can't see any useful information there.
You can't simply edit tiapp.xml and remove the appc/acs attributes to solve this problem
this problem will not occur if you run your app on IOS simulator.
Also, don't downgrade to Titanium 4.X. That means your app won't run at the latest devices.
I typically use the Titanium CLI to build my project using a command like the following:
ti build --skip-js-minify -p ios -T simulator -Y iphone --retina --tall --sim64btin
Now that Titanium 3.4 SDK is out and supports iOS 8 and XCode 6, I expected that I would be able to easily launch my app in the new simulators. But currently it seems to be defaulting to the iPhone 4s sim.
What am I missing?
There are several ways to do this, including importing the .xcodeproj into XCode, but I find my way to be more convenient personally. It's not perfect, but this is what I'm currently doing, and how I got there.
Some inspection of the Titanium SDK source reveals that the CLI uses a binary called ios-sim to actually launch the simulator. Some googling will reveal that this is a node.js package. I happened to have this installed, but I'm not sure if it was installed by Titanium or not - the build script uses a binary that is packaged in the SDK.
Console output:
RalphsMBP:~ trey$ which ios-sim
/Users/trey/npm/bin//ios-sim
RalphsMBP:~ trey$ ios-sim --version
2.0
The documentation says this about Xcode6:
Supports Xcode 6 only since version 3.x.
So step 1:
sudo npm install -g ios-sim#3.0
ios-sim --version
You should now be at 3.0.0.
My first thought was to replace the binary in the Titanium SDK with the newly installed binary from npm. I thought that perhaps the arguments to ti build would be passed directly to ios-sim. This turned out to be a dead end (The builder.py script is a mess in my opinion - rewrite it already!)
Fortunately it's still pretty easy to write a build script to launch in your simulator of choice using the new devicetypeid option to ios-sim. Use ios-sim showdevicetypes to get a list of valid device type ids. This is my iPhone 6 build script:
ti build -b --skip-js-minify -p ios && ios-sim launch ${project_path}/build/iphone/build/Debug-iphonesimulator/${project_base_name}.app --devicetypeid com.apple.CoreSimulator.SimDeviceType.iPhone-6
The variables are part of the sublime text build system, but you can apply the concept any way you want. The -b flag is --build-only, and I think the rest is pretty self explanatory.
I've got DalekJS running really well on WinLin, but am interested to know exactly what the process is for running it on iOS.
http://dalekjs.com/docs/ios.html
When running on Windows, for example, I install the DalekJS npm globally, and then install the IE web-driver, before executing my test suite.
On iOS am I expected to do the same thing? Can you install NodeJS on an iPhone? Is there a difference in doing it on the actual device, vs doing it through the emulator?
Also, what are the current obstacles in making it run on iPad?
Thanks!
Dalek will not run on the IPad/Iphone etc. itself (neither will or must NodeJS), it uses the native debugging tools that come with the dev environment through Appium.
Unfortunately, due to some changes that happened in MacOS 10.8 & 10.9 (Changes in the user rights management, etc.) it can only do this in the simulator. We are working on bringing back support for "real" devices with the next version of DalekJS.
We Really need some help on this one:
We've Struggled with all the Apple Mumbo-Jumbo for the Last two months and can't seem to get our APP on the APPStore...
Right now my problem is after Validating the ARCHIVE compilation and sharing it.. in the Submit Process I Get -
"An error occurred uploading to the iTunes Store"
I Really don't Know what I'm doing wrong and don't seem to find ANYTHING on the Internet that solves the problem...
I've been stugling with this for over a week now... I've tried:
Creating a new Distribution Profile for Code Signing.
Checking All the Target Settings over and over.
Changing the FTP mode from Passive to non-Passive
Connecting from different networks
Reinstalling Xcode4
some other Work Arounds like Downloading the application Loader (Haven't installed it yet, but I Don't Know if I Should)
Please help us, what do you think could be the problem?
Thanks
Hernan
If you are unable to upload Apps to Apple and installed the JavaOSX update (April 3, 2012) this may help you regain your ability to upload Apps:
You can work around this issue by re-creating the old Java 1.5 symlinks:
cd /System/Library/Frameworks/JavaVM.framework/Versions
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0
Edit Oct 5, 2012 Oracle's Java 7
Elaborating on Hackmonford's comment below.
This exact error message also occurs with Oracle's Java SE 7 1.7.0_10 package installed. To resolve, open "Java Preferences" and either change the order to have Apple's Java SE 6 first, or untick Oracle's Java 7 while submitting to the app store. Verify your change by opening the Terminal:
prince$ java -version
java version "1.6.0_35"
I was having this problem this week, and installed the Java for OS X Lion 2012-002 update, and the problem cleared up. Resetting disk permissions had no effect.
This just happened again.
For OSX 10.8.2 users (does not have Java preference), the only way to fix this is to uninstall oracle jdk.
cd /Library/Java/JavaVirtualMachines
sudo rm -rf jdk1.7.0_09.jdk/
I had also a JavaVM / JRE issue. I have installed the JDK 7 preview from Oracle and that mixed up the upload process which told me the known "An error occurred uploading to the iTunes Store".
A quick check of /var/log/system.log (e.g. using tail in a terminal: tail -n 100 /var/log/system.log) brought up the following error message:
Java 1.5, 1.6, or 1.7 is required. Currently, java is the default java version. Please upgrade.
I had installed the MacOS Preview of JDK 7 directly from Oracle. To fix this issue, simply launch the Java Settings app in Utilities and uncheck JDK 7 from Oracle. Of course you should have an alternate JRE from Apple. See the screenshot how my configuration looks. The upload works for me now.
The odd thing is that the Oracle JDK isn't recognized as Java 1.7 by Apple. This seems like a bug.
UPDATE:
The GUI tool was removed from MacOS. Now, the only solution I know of is to remove the JDK 1.7 folder manually. See the JDK 7 docs how to do this:
Navigate to /Library/Java/JavaVirtualMachines and remove the directory whose name matches the following format:
/Library/Java/JavaVirtualMachines/jdk<major>.<minor>.<macro[_update]>.jdk
For example, to uninstall 7u6:
% rm -rf jdk1.7.0_06.jdk
A bit late, I know - but for anyone still having this problem - Look in your /var/log/system.log log file. In my case the problem was that the iTMSTransporter script (used by the Organizer when uploading the file) used 'awk', and I had to replace it with '/usr/bin/awk'.
Completely solved my problem.
Y.
Just in case this is useful for anyone else - for me it was that the Java JRE was not up-to-date. I checked the console and Application Loader was complaining
I had this problem today after installing latest XCode.
I fixed it by running software update and installing latest Java Update.
I tried the same thing as Hernan, but even with application loader 1.3 I wasn't able to upload.
I noticed that this has happened after installing OSx Lion and upgrading XCode to 4.1!
I followed Joe's tip and I found out that JAVA wasn't even installed.
Follow this blog entry:
Unable to Upload App to App Store
My mbp now run Xcode4.2(4D199) on Lion, I installed the latest java for Lion. And finally I sovled this issue.
Many guys said, he can used the old Application Loader app to upload the apps. so I guess the problem is the latest Application Loader app(2.4.1 (190)), and the fact told me I am right
Okie, in short words:
Here is the solution:
1.I hope you guys do not delete the old Xcode(4.1). We Should pick up the old version Application Loader app.
cd <Install Xcode app>/Contents/Resources/Packages
cp ApplicationLoader.pkg ~/Desktop/
Now, you get the ApplicationLoader package.
2.Install the old one.
Tips: you can remove the latest Application Loader app in path: /Developer/Applications/Utilities/ or just remane it.
That's All.
Hope this way can help you and enjoy the new Xcode4.2. Also hope apple developer can saw this problem and test the latest Application Loader app more.
No Problems submitting to AppStore on April 1st. Issue occured on April 9th. Installing the Java for OS X Lion 2012-002 update via Mac-OS software updater and rebooting the machine fixed it.
Just update to the latest JAVA at your Mac Software Update.
Here is the steps to resolve this issue:
To start with I had installed Oracles Java 1.7 JDK, which was really messing things up.
Went to Finder>Applications and entered in Search box - JavaAppletPlugin.plugin
Right clicked and removed to trash.
A check in Terminal for Java version still showed Java 1.7
my-imac:~ my$ java -version
java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
1. Finder>Library>Java>JavaVirtualMachines showed the 1.7 SDK (make note of exact name of the Directory name)
Just in case anything went wrong I copied the 1.7 SDK folder to my desktop before doing the next item
2. In terminal type
cd /Library/Java/JavaVirtualMachines
3. You should now be in that directory
sudo rm -rf jdk1.7.0_06.jdk (or whatever the exact name of the directory is in step 1.)
You may have to enter your administrator password
The directory should now be deleted and you can verify in Terminal by
java -version
Mine now showed "Java 1.6_xxx"
Went into Xcode Organizer and distributed my app to the iTunes store without a problem. Whoo,hoo!