The AIR SDK is usually only referenced by major and minor version number, but there are important differences in the numbers way to the right.
How can I inspect my installed SDK and know for certain which exact version it is?
If you're on Windows:
Navigate to the location of the AIR SDK.
Open the /bin/ subdirectory. You should see a file named adl.exe.
Right-click on adl.exe and select Properties from the context menu.
In the Properties dialog, click the Details tab.
The Details tab contains a property named "File Version" with a value that shows the full version of the AIR SDK (e.g., 3.5.0.1060).
If you're on a Mac (or on Windows), you could just create a bare-bones AIR app and add this line of ActionScript:
trace(NativeApplication.nativeApplication.runtimeVersion);
When you test the file in your IDE of choice, you should see the full AIR SDK version in your IDE's output panel.
Mac OS X
Open the /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Info.plist text file and locate the CFBundleVersionentry. The corresponding string entry represents the version of AIR, for example:
CFBundleVersion
26.0.0.127
https://helpx.adobe.com/air/kb/determine-version-air-runtime.html
For the most definitive answer, directly ask AIR SDK what version it is (adt.jar is the AIR SDK's packager):
java -jar C:\air_sdk\lib\adt.jar -version
Which prints the full version number:
3.9.0.1030
How to find the adt.jar file on your system? Often you'll have an environment variable set pointing to your AIR SDK, such as AIR_HOME or AIR_SDK_FOLDER, so you can use that in your command:
Windows:
java -jar %AIR_SDK_FOLDER%\lib\adt.jar -version
Or on a Mac / Linux:
java -jar $AIR_SDK_FOLDER/lib/adt.jar -version
From Mac
Write the following console command to check the current version of Adobe AIR SDK:
%AIR_SDK_FOLDER%/bin/adl -version
Correction to the above, it's adt, not adl to spew the version number to the commandline on Mac (and probably Windows too).
So:
%AIR_SDK_FOLDER%/bin/adt -version
Related
Just installed (copied over the app from the downloaded dmg) DevCenter 1.6 on my mac, running macOs Sierra 10.12.6 with jdk 8u152 installed. The application loads a UI (splash screen then a couple of checkboxes in a window for getting started) but the UI is frozen (with the splash screen still there). No response to mouse clicks or keyboard. Also can't click on the app name in the menu bar. The app however is not labeled "Not responding" by activity monitor.
So far I've tried -
Looking at the logs both in the app folder and in ~/.devcenter. Nothing fishy there
Running the app from a different user account - same issue there
Deleting all datastax and devcenter related files (searched by name) on my machine and fresh start - still the same issue
any ideas what I could do here?
I was running DevCenter on a previous mac with the same config / os version but a slightly older JDK, never had issues then.
On OSX, you can specify which version of Java DevCenter uses so that you do not need to downgrade your global Java version.
Right-click on Devcenter.app
Click "show package contents"
Open Contents/info.plist
At the bottom of the file, there's an Eclipse key with lines commented out explaining how to specify the version of Java. Uncomment the line and specify the version of Java that you want DevCenter to use.
Save & Re-launch DevCenter
The updated info.plist file should look something like this:
<key>Eclipse</key>
<array>
<string>-vm</string><string>/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java</string>
</array>
I reached out to someone at Datastax and learnt that complaints have surfaced about this behavior when using DevCenter with jdk 8u152.
For now, I've downgraded to jdk 8u151 and that fixes the issue.
Without downgrade the Java version
Scenario
I couldn't create any connection and press buttons and everything was frozen; Changing the swt plugin in the DevCenter plugin folder worked. This was my configuration:
DevCenter version DevCenter-1.6.0-macosx-x86_64
Mac OSX version 10.14.6
JDK Version jdk1.8.0_231.jdk
Steps to fix it
From here download the version 3.108.0. (This version works for me)
Rename the file downloaded as swt.jar (short name)
[Optionally] create a backup of the current swt plugin jar of the DevCenter
cp DevCenter/DevCenter.app/plugins/org.eclipse.swt.cocoa.macosx.x86_64_3.103.2.v20150203-1351.jar ~/Desktop
Replace the plugin with the swt.jar downloaded
mv swt.jar DevCenter/DevCenter.app/plugins/org.eclipse.swt.cocoa.macosx.x86_64_3.103.2.v20150203-1351.jar
Startup DevCenter
Finally it worked
I've downloaded a copy of the Worklight CLI installer from here, specifically the installer for 6.2.0.1 (I'm aware this isn't current, I need an older version to debug a specific problem). I am attempting to install it on OS X Mountain Lion (10.9).
However, I seem to be having problems installing it. When I unzip the installer, I get an install_mac.app/ directory. I open this with open install_mac.app from the Terminal. However, when I've clicked the button to enter the administrator password (which is accepted), the installer then shows this screen for about 5 seconds, then disappears completely (is no longer running). It appears that at this point it has crashed (although there is no stack trace or similar in the terminal).
How can I debug/fix the installer? Alternatively, is there a way to manually install the CLI?
My $JAVA_HOME is set to /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home. /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin/java -version gives:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
On OS X the CLI installer does not provide the ability to install from command line.
However what you could do is to manually extract it instead of using the installer, and in order to compensate on the actions that the installer is doing (node registration, PATH handling), put the extracted content at the same location of the currently installed CLI. Replace it.
The above .zip is inside the "resources" folder, next to the OS X/Windows/Linux installer files.
How can I log all system information about Titanium and Alloy configuration and all other information about the current build, version numbers etc?
I'm looking for something similar to PHP's phpinfo.
You can log it using the methods mentioned from #daniula and #Wahhas_mirza. But you can use the command line tools if needed to display information that relates to Alloy and Titanium.
If you open the Terminal Window, enter the keyword alloy, you will then see the usage for the command.
alloy
To view what version of alloy your project is using enter:
alloy -version
For Titanium related information use the keyword ti
ti
which then displays the usage for:
Titanium Command-Line Interface
As an example: ti info will display all relevant information that pertains to your Titanium setup
I hope this helps.
There is nothing like phpinfo() in Titanium. If you really want to print all information about your platform you can try something like this:
for (var i in Titanium.Platform) {
if Titanium.Platform.hasOwnProperty(i) {
Ti.API.info(i + ': ' + Titanium.Platform[i]);
}
}
Start a terminal session in studio ( or switch to app's directory in a console). Type ti info. You'll get output similar to the following
Titanium Command-Line Interface, CLI version 3.2.3, Titanium SDK version 3.2.3.GA
Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved.
Please report bugs to http://jira.appcelerator.org/
Operating System
Name = Mac OS X
Version = 10.9.3
Architecture = 64bit
# CPUs = 8
Memory = 8.0GB
Node.js
Node.js Version = 0.10.28
npm Version = 1.4.9
Titanium CLI
CLI Version = 3.2.3
node-appc Version = 0.2.1
Additionally, you'll get a list of all your simulator/emulator configurations, certificates, provisioning profiles and any config errors (if any).
Here you go
Ti.API.info('I want to show the data in console');
Thanks
I never used anything Air but Adobe Muse and Adobe Edge, and they both have installer packages.
I'm running Windows 7 and I followed these steps below.
Download crunchapp from http://crunchapp.net/ and extract to any location
Install Adobe Air SDK by going to their site.
Unzip it to appropriate folder (I extracted to C:\Program Files\Adobe\Adobe AIR SDK)
Right-click on "My Computer" in the Start menu and select Properties.
Click on "Advanced System Settings" on the left hand side menu
Select "Environment Variables" and add two new system variables as below
adl
[change path to your extracted Adobe AIR SDK\bin\adl.exe file]
(I used - C:\Program Files\Adobe\Adobe AIR SDK\bin\adl.exe )
adt
[change path to your extracted Adobe AIR SDK\bin\adt.bat file]
(I used - C:\Program Files\Adobe\Adobe AIR SDK\bin\adt.bat )
RESTART PC (this caught me out)
Open command Line Interface and navigation to C:\Program Files\Adobe\Adobe AIR SDK\bin\
type in adl [full path to Crunch folder]application.xml
Enjoy Crunch!!!!
HTH
Ralph
In my Windows machine, this is what I did just now (because, I also did not know where to start):
You need to download the Adobe Air SDK
Extract its content and I followed this: http://chisflorinel.blogspot.com/2007/06/installing-adobe-air-on-windows-vista.html
After that, I opened my command line, then went to the Crunch! folder, then type the command:
adl application.xml
I've just downloaded libogg from http://www.xiph.org/downloads/ (http://downloads.xiph.org/releases/ogg/libogg-1.3.0.tar.gz) and I'm now trying to compile the Ogg.xcodeproj project provided in that package. When I try to build, I get the following error:
The run destination My Mac 64-bit is not valid for Running the scheme 'Ogg'.
The scheme 'Ogg' contains no buildables that can be built for the SDKs supported by the run destination My Mac 64-bit. Make sure your targets all specify SDKs that are supported by this version of Xcode.
I get a similar error if I attempt to build the static library instead of the framework:
The run destination My Mac 64-bit is not valid for Running the scheme 'libogg (static)'.
The scheme 'libogg (static)' contains no buildables that can be built for the SDKs supported by the run destination My Mac 64-bit. Make sure your targets all specify SDKs that are supported by this version of Xcode.
Again, this is just opening the project in Xcode 4.3.2 for the first time and attempting to build. I've made no changes to the project file at all.
Can anyone point me in the direction of a solution to get this to compile?
In my case, the Xcode project was linking against an old SDK on an old architecture (OS X 10.5 PPC, whereas I have OS X 10.8 Mountain Lion x64).
To fix this in Xcode 5, select the top-level project in Xcode (the top-most node in the project folder pane, with the blue "A" icon) followed by the Project. Change Architectures to something suitable for your current system, such as Native Architecture of Build machine and change Base SDK to an SDK currently installed in your Xcode environment, such as OS X 10.8.
Here is a screenshot of my project to help you find those settings (following the highlighted parts: kisshelper > kisshelper > Architectures):