Having a recurring issue when trying to create an AIR Captive Runtime using the latest AIR 3.5 SDK.
Publishing in Windows 7 from Flash CS6.
Most of the time AIR will only create a .tmp folder and NOT an .app folder
And the .exe in the .tmp folder sometimes works, other times gives an error message on launch saying a wrong version of air exists.
At other times the .tmp folder is totally empty.
Anyone PLEASE with any ideas or suggestions greatly appreciated!
After running into this problem again, I found that the actual solution is:
1) EDIT the adobe air application descriptor xml file for the project, make sure the following tag is uncommented and includes the extendedDesktop profile:
<supportedProfiles>desktop extendedDesktop</supportedProfiles>
2) Clean your project
3) Then export release build from flexbuilder and select captive runtime option.
The solution listed below was misleading (I had actually included the step described above and not included it in my description below ). Command Line execution was a red herring.
I solved my problem by using a command line request and following the instructions at this website.
Executing the command line request from the bin-release temp folder on my machine I modified the following to my desktop settings:
c:\path\to\air3sdk\bin\adt.bat -package -storetype pkcs12 -keystore c:\path\to\certificate.p12 -target bundle myapp.exe myapp-app.xml -C . myapp.swf
Related
I have downloaded both apktool_2.1.1.jar & apktool_2.0.0rc4.jar from https://bitbucket.org/iBotPeaches/apktool/downloads and pasted it in C://Windows. Yet when I run apktool in cmd, it returns:
C:\Users\arpit>apktool
'apktool' is not recognized as an internal or external command,
operable program or batch file.
Any help will be appreciated.
->Download Windows wrapper script from here https://raw.githubusercontent.com/iBotPeaches/Apktool/master/scripts/windows/apktool.bat
(Right click, Save Link As apktool.bat)
->Download apktool-2 https://bitbucket.org/iBotPeaches/apktool/downloads
(find newest here)
->Rename downloaded jar to apktool.jar
->Move both files (apktool.jar & apktool.bat) to your System32 directory (Usually C:\Windows\system32)
If you do not have access to C:\Windows\system32, you may place the two files anywhere then add that directory to your Environment Variables System PATH variable.
->Try running apktool with admin previlages via command prompt
Apktool is a tool for reverse engineering 3rd party, closed, binary Android apps. It can decode resources to nearly original form and rebuild them after making some modifications. You will find apktool indispensible if you want to extract resources (i.e. images from an Android application. Actually, the tool has no competitors at all!)
An online version of the apktool is available here: www.javadecompilers.com/apktool
I had submitted the application via Application Loader 3.1. It shows "invalid package Applications built with SDK 9.0 or later must be packaged as proper IPA files."
I had received an Email on Sep 12 from Apple which allow to submit apps built by Xcode 7 GM.
make a folder with name Payload.
put the compiled files into Payload folder.
compress folder to Payload.zip file, than change to Payload.ipa.
Ran into the same problem today. Turns out Application Loader 3.2 now requires the file to be .ipa only. It for some reason still accepts .zip files but will fail with this error. So just change the file extension to .ipa, assuming the contents were properly generated.
Try convert your .APP to .IPA by command line:
/usr/bin/xcrun -sdk iphoneos PackageApplication -v "${RELEASE_BUILDDIR}/${APPLICATION_NAME}.app" -o "${BUILD_HISTORY_DIR}/${APPLICATION_NAME}.ipa" --sign "${DEVELOPER_NAME}" --embed "${PROVISONING_PROFILE}”
I was having same problem all you need to do is to submit .ipa file and it will work like a charm.
Simple Trick worked for me:
Archive and Export the build from organizer. Select “Save for iOS AppStore Deployment”.
This will generate a ipa file that application loader accepts and uploads without any problem.
I have installed SenchaSDKTools-2.0.0-beta3-windows on my windows Xp 32-bit.
following is the command I am running on command prompt.
C:\Program Files\SenchaSDKTools-2.0.0-beta3>sencha app create MyApp c:\xampp\htdocs\sencha\myapp\
Giving following error
[ERROR] the current workind directory (C:\Program
Files\SenchaSDKTools-2.0.0-beta3>) is not valid SDK directory. Please
'cd' in to a SDK directory before executing this command.
environment variable has been set following way.
Variable name : Path
Value : C:\Program Files\SenchaSDKTools-2.0.0-beta3
can anyone figure out what exactly wrong in this process ?
*****Sencha Touch setup Guide steps(in Window)******
Download Sencha Touch SDK Tool. (http://www.sencha.com/products/touch/download/ -->SDK Tools Beta for Developers). Run .exe file. It will install tool to default path. (i.e. C:\Program Files\SenchaSDKTools-2.0.0-beta3)
Download Sencha Touch SDK. (Download openSource version file licensed under GPL.).
Extract SDK you just download in step 2.
Open Command line terminal (start->Run->type cmd). Change directory path to SDK path as you just extracted in step3.
Verify that Sencha Command is working properly on your machine. So Type Sencha.
E.g. sdkPath>sencha
you will see "Sencha Command v2.0.2" message with other sencha command detail.
Create app in your web directory by typing following.
E.g. sdkpath> sencha app create firstSenchaApp "path/ to/ www"
(If you have tomcat 7 installed in your computer, give path to \apache-tomcat-7.0.30-windows-x86\apache-tomcat-7.0.30\webapps)
Note: There must not be space in directory path name. _(underscore),- (desk) are allowed.
If app is not generated in step 6. There might be an error. There are as follow:
If error message appear is "sencha' is not recognized as an internal or external command, operable program or batch file.”, follow these steps to troubleshoot:
The path to SDK Tools directory is prepended to your system's PATH environment variable.
From the terminal, run
echo $PATH or echo %PATH% .
The SDK Tools directory should be displayed in part of the output. If this is not the case, add it to your PATH manually.
The environment variable SENCHA_SDK_TOOLS_{version} is set, with the value being the absolute path to the installation directory mentioned above.
For example: If the installed version is '2.0.0-beta2', a SENCHA_SDK_TOOLS_2_0_0_BETA2 must be set.
From the terminal, run
echo $SENCHA_SDK_TOOLS_2_0_0_BETA2 or echo %SENCHA_SDK_TOOLS_2_0_0_BETA2% on Windows.
If the output is empty, set the environment variable manually.
Wrong Current Working Directory
A common mistake is not running Sencha Command within either a valid SDK directory or an application directory. If the current directory is not a SDK or application directory, "sencha" command will fallback to backwards-compatible mode. As of SDK Tools release "2.0.0-beta2", you should see a clear warning in such case:
"The current working directory (...) is not a recognized Sencha SDK or application folder. Running in backwards compatible mode." So in this case follow proper step as mentioned above.
Reference:
http://www.sencha.com/forum/showthread.php?192169-Important-SDK-Tools-Sencha-Command-Update
There is an invisible file that you need to copy, called .senchasdk. Make sure it is in the folder.
I think you're having the same problem I had; I had attempted to run 'sencha app create...' from the folder containing sencha.bat. Instead, you need to run 'sencha app create...' from the sencha-touch-2.0.1.1 folder (which contains the .senchasdk file).
See this previous SO question!
Save my days.
By the way, if you can't extract the sencha-cmd to sdk tools, try to extract on other location and copy the folder [3.0.0.250] to your sdk tools > [bin] folder.
hope this helps.
I made a script to copy,rename and change Bundle Id of a project from command line, after that process, my next step is to change the code signing of the project to point to the new certificates.
Is there any way of doing this from command line?
Edit: I just saw that that info is stored on the .pbxproj, how can I change that file?
You can re-sign a build using the following:
export CODESIGN_ALLOCATE=`xcode-select -print-path`/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate
codesign -f -s "iPhone Developer" -vv Example.app/Example
If all you have is an IPA, just unzip it, it's a normal zip file with a single Payload directory containing your application.
Edit:
If you need to change an Xcode project itself, an Xcode project is just a bundle, change into the directory and open the project.pbxproj file. You should be able to simply use sed to find and replace the developer identity.
There may be better options, such as supplying the setting on the command-line to xcodebuild. If you give more background on what it is you are trying to do, you may get better suggestions.
I can't figure out what the difference is between the 7z.sfx file available with 7zip and the downloadable 7zsd.sfx from the developer's site, which is not bundled with 7zip. The 7z.sfx appears not to honor my request to include the config.txt file I created for it, but the 7zsd.sfx inclusion method works perfectly.
7zip comes with 7z.sfx bundled. The application history.txt in the program files directory shows that 7zsd.sfx used to be bundled with 7zip back in 2005. 7z.sfx is referred to as "uncompressed SFX" in the history.txt file as well.
This is the config used:
;!#Install#!UTF-8!
InstallPath="C:\\ProgramData\\IT"
GUIMode="2"
;!#InstallEnd#!
This is the syntax I'm using and the responding behavior:
C:\Users\<me>\Desktop\Updater\Recorder>copy /b 7z.sfx + config.txt + "RecorderVer0.0.0.4".7z "RecorderVer0.0.0.4".exe
7z.sfx
config.txt
RecorderVer0.0.0.4.7z
1 file(s) copied.
The same response occurs with the use of 7zsd.sfx indicating that indeed the config file included is being utilized. However, when executing the 7z.sfx created RecorderVer0.0.0.4".exe the prompt for where to install the contents of the 7z archive is prompted for. Using the 7zsd.sfx created RecorderVer0.0.0.4.exe version directs files to the config set location without any prompting as desired.
To my knowledge 7z.sfx is not downloadable via the developer's site, but I may be wrong. His official page is no longer available, but the information provided from the Internet Archive should be adequate.
I had this previously posted as a comment to my own question.
I found the answer to my question in 7-Zip documentation of all places! :) Looks like there are a total of 4 sfx modules and these are the differences:
SFX_Module : Description
7z.sfx : Windows version.
7zCon.sfx : Console version.
7zS.sfx : Windows version for installers.
7zSD.sfx : Windows version for installers (uses MSVCRT.dll).
Source: http://sevenzip.sourceforge.jp/chm/cmdline/switches/sfx.htm
Acquiring the 7zS.sfx and/or 7zSD.sfx stuffs is easy:
The installers are on the official download page. Just look for keyword 7-Zip Extra. Version 9.20 for example is https://www.7-zip.org/a/7z920_extra.7z
Just in case anybody stumbles across this post looking for the 7zS.sfx and 7zSD.sfx, you can find the 7z_extra files for the (currently) latest version at http://sourceforge.net/projects/sevenzip/files/7-Zip/9.22/7z922_extra.7z/download.
I was also looking for the other sfx modules and managed to find them in the related LZMA SDK archive on the actual 7-zip website:
https://www.7-zip.org/sdk.html
Download the latest version of the LZMA SDK and look in the bin folder.