This is my first time I ever created an air installer. When I clicked on "Export release build..." and clicked on finish, it is creating "projectname.AIRI" file instead of "projectname.air" file.
I confirm below check
I did not change the default name
Tried to find using what an airi can open with, but there is nothing as such
Renamed airi to air and tried to open the file (icon has changed to air installer) but it gave me error "corrupted installer"
Can some one help me what to do? Is it that complicated?
There are two options in the "Digitial Signature" window
Export and sign an AIR file with an digital certificate
Export an intermidiate AIRI file that will be signed later
The options are very clear. I have not read the options clearly and went ahead to option 2 which creates AIRI file as it says.
I overseen the "Create..." button next to the "browse" button to select the digital certificate and I thought I must have a digitial certificate already and I dont have one.
Its simple, just click on the create button to create one certificate and the same certificate can be used for other pprojects as well.
Related
Edit 1: I am using the floobits plugin (latest release), uninstalled and installed again from the package manager. I am not getting a traceback but an error window with the following error message: Unable to join workspace. CERTIFICATE_VERIFY_FAILED unable to get local issuer certificate (_ssl.c:1124).
Edit 2: I had tried the Package Control Upgrade package and Staisfy Dependencies, but that did not help fix it.
I was able to fix it (answer below).
I have been stuck on this issue for days now. When I try to connect to a floobits workspace in sublime text, I get the error message that CERTIFICATE_VERIFY_FAILED unable to get local issuer certificate (_ssl.c:1124).
I searched about this a lot but I don't know what's wrong anymore.
I started by upgrading certifi and pip itself.
Then I read somewhere that I should check if OpenSSl(and the requests library of py) and cURL can open the URL (floobits.com) since the workspace is hosted there. curl returned no errors but OpenSSL (and requests) wasn't able to verify, gave the same error.
So I downloaded the certificates from the website on opening it in chrome. I downloaded all three certificates (for the root, intermediate and the website itself), and appended them to cacert.pem inside the certifi package folder. After that, when I ran it, OpenSSL was able to open it (and the requests library too, got a 200 response code).
But, floobits still wasn't able to connect and gave the same error. I know that there is nothing wrong with floobits.com and the sublime extension since a friend can still open the workspace without problems.
Please tell me what I can do to fix this.
So I managed to 'solve' the problem by bringing Sublime back to a fresh state and then copying my files again. Answering here if anyone gets this problem.
Method:
Go to the Sublime > Preferences > Browse Packages
In this folder, copy and backup the 'User' folder to someplace else.
Delete all the folders in this location (Sublime need not be closed during this but it's best if you do close it)
Copy the backed-up 'User' folder back here (remember the location where you deleted, %AppData%\Roaming\Sublime Text 3\Packages (for Windows))
All set, you now have a fresh installation of sublime.
Sublime will start installing all packages again, wait for it to finish and resume work.
This solved the problem I was having. Unfortunately, I couldn't track down the problem.
I am currently trying to install PDFCreator 1.6.2 on my computer (Windows 7 64bits).
I have to use this specific version and not another one due to compatibility issues with another program.
I launch the setup in administrator mode, check "Expert settings"
I accept the agreements
I choose the Server Installation
I Click on "next", let the default printer's name "PDFCreator"
I do not check the box "Windows 2000/XP/2003 - 32bit" and click next
I choose the directory in which I want to install it (C:...\PDFCreator)
I just uncheck "PDFArchitect" and let everything else by default
I let the program's shortcut name in the start ùmenu folder by default (PDFCreator)
At the next page I also let everything by default (create a desktop icon for all users, create an entry in the Windows Explorer context menu)
Click on next, the summary of the installation is displayed, click on Install
The bar goes through the end, then "Create an entry in the Windows Explorer context menu" is displayed and a error pop-up appears which says "During the printer installation errors have occured. A detailed description can be found in the file "SetupLog.txt" in application path.
I click on "OK", and the last setup page is displayed. I uncheck all the boxes (launch PDFCreator, SetupLog.txt, show help), click finish and the setup crashes.
PDFCreator does not appear in the printers and if I try to add one manually by clicking on "add a printer", select "add a local printer", "create a new port", port type : "pdfcmon", I can click on "next" but it has no effect so I am a bit stuck.
Do you have an idea why does the installation crashes ?
Is there a workaround ?
The content of the file "SetupLog.txt" is available here :
SetupLog.txt
I've so far been unable to reproduce your problem despite numerous test installs (and uninstalls) of v1.6.2 on a Win7 64-bit box. Your posted log indicates that the process successfully created the pdfcmon port, but then apparently lost it afterwards (or else never created it, but misread its own return status):
Install printerport:
Portname : pdfcmon
Result: Success
[...]
InstallPrinter:
Printername: PDFCreator
Drivername : PDFCreator
Portname : pdfcmon
Result: Error 1796 = Le port spécifié est inconnu
It's reasonable to assume that nothing useful will occur beyond that point, so you'll need to address error 1796 first. A quick Google of that error code leads to a number of queries at PDFForge.org about it:
http://forums.pdfforge.org/search?Search=1796
Not all received replies, but one involving 2003 Server in particular did:
you need the latest service pack for Server 2003, then it should work.
Elsewhere in your log file I see references to some older software (e.g. Internet Explorer version: 9?) which leads me to think that you might want to doublecheck that all your relevant service packs and software are up to date first, then try your installation again.
Nevermind, I gave up installing PDFCreator, I have a server on which I could install it without any problem so the problem is kinda fixed
I still don't know why it crashed but that's not relevant anymore.
Sorry for making some of you wasting their time
I recently switched to a different computer for my programming. it was another collegue's computer and was not reformated. i installed xCode on it. This is the first time i've tried to update an app of ours on this machine. i archived w/out errors and i validated w/out errors. when i go to submit, i get these two errors:
*Unable to create configuration directory: /Users/username/.itmstransporter
*Your home folder must be writable in order to save run-time configuration data. Please
ensure your home folder exists and is writable.
i am not a mac OS person and can barely get around on a mac. a coworker checked and i do have read/write permisions for /Users directory.
can i fix this or do i need to re-install xCode or the OS?
I belive this is because your username on that machine can not write to your home directory (some how)..
Try opening a finder window and "get info" on your home folder. (from finder, Cmd-N opens a window, right click on the folder in the left that is your user name, that is your home folder, and select get info. Right click might not work, if it does not work, use ctrl-click.)
In the "get info" dialog, at the bottom you will see "Sharing & Permissions" you may have to turn the triangle by clicking on it. In the list, make sure your username has Read & Write prifileges, if not, you need to add them by logging in as an admin and changing them.
This photo is just for reference, but you can see justin (me) has Read & Write, that is what you need on your home directory.
I get this error when trying to build a project using Team Build (MSBuild) on TFS 2010:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1970):
Cannot import the following key file: CCC.pfx.
The key file may be password protected.
To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_C00C673BBB353901
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1970):
Importing key file "CCC.pfx" was canceled.
It all builds OK in Visual Studio 2010. The assembly is signed with a PFX file. Usually in Visual Studio we are prompted for the password the first time we build, but then never again...
I've tried running:
sn -i companyname.pfx VS_KEY_3E185446540E7F7A
as other replies as suggested in Stack Overflow question Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'. I've tried importing into the personal certificate store as suggested in Stack Overflow question Using MSBuild to sign ClickOnce or assembly results in error MSB3321. But all to no avail, still the same error.
How do I do it? Do I have to somehow add the certificate to the Windows account the build service runs under or something like that?
Alternatively, how do I make the build done in Team Build not use signing? I just want to check it compiles and run the unit tests. I don't need signing for that.
You need to adapt this answer to your specific. Something like:
sn -i companyname.pfx VS_KEY_C00C673BBB353901
What I did is not that elegant, but works: log in as the user that runs msbuild on the build machine, manually invoke msbuild, and then type in the password when prompted. It'll now be saved in that user's certificate store, and now the builds can run unattended.
What finally fixed it for me was making the account under which TFS Build service runs an administrator on the local machine.
Don't know though if any of the other stuff I was trying before also needs to be done to get it working. But before it was admin it didn't work after it became admin it worked.
I was getting the same error, and after reading your "administrator" comment - I just ran VS Command Prompt as Admin and it now works fine.
I have faced similar issue
Scenario 1: While building project in local system
In my case i was getting the manifest signing error once i download the project from TFS and build it.
To avoid this issue I right clicked on the project ==> Properties ==> Signing
then unchecked "Sign the ClickOnce Manifests"
OR
You can click Select from store button and select your login id from the dialog box open.
OR
You can install the PFX file manually and later click on More Options button to install those certificate.
Scenario 2:- Manifest error during Build
Here to resolve this error i first clicked Select from store button and select my login id from the dialog box .Then I committed that project in TFS first and then run the build.
I had following settings:
<PropertyGroup>
<SignAssembly>false</SignAssembly>
<AssemblyOriginatorKeyFile>MyKey.pfx</AssemblyOriginatorKeyFile>
</PropertyGroup>
Assembly signing was turned off, but AssemblyOriginatorKeyFile caused error during manifest sign. Removed AssemblyOriginatorKeyFile to fix it.
I have been unable to overcome this error in Application Loader. I've quit, restarted, tried different computers - it's like the server is hung up on an op that I never initiated and it won't time out. Has anyone seen it before and beaten it?
Basically, you need to clear out the transport tokens. This can happen if you were to close out of Xcode while in the middle of submitting an app to iTunes Connect.
The token files now appear in the
Library/Caches/com.apple.amp.itmstransporter/UploadTokens/ subfolder of the given user's home directory. Which, honestly, is a better place for them anyway.
Delete any .token files in this directory.
--
If you are unable to find the .token files, this is because they are hidden in Finder. To hide/show hidden files in Finder, use the following Terminal command (TRUE = UNHIDE, FALSE = HIDE):
defaults write com.apple.finder AppleShowAllFiles TRUE;killall Finder
You need to clear out the transport tokens.
Open Terminal on your Mac, and paste:
rm /Users/<username>/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/*.token
That should clear the stuck token. After this, try uploading the build again.
It might be because Xcode crashed as you were uploading your app. Either, all you need to do is delete the token files:
Open Terminal on your Mac, and paste:
rm ~/.itmstransporter/UploadTokens/*.token
That should clear it. If it still doesn't work (at this point you should try re-uploading your app), run that command on Terminal again, or manually go to...
/Users/<username>/.itmstransporter/UploadTokens/
...and delete all the .token files.
Hope that helps!
token was in here
/Users/(user_name)/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/
Appreciated #WrightsCS 's answer It helps me to overcome Application Loader issue.
I would like to highlight one more thing here.
I proceed as per #WrightsCS answer and it resolved Application loader error:
Can not proceed with delivery: an existing transporter instance is currently uploading this package
But I found one more issue after removing all tokens from
/Users//.itmstransporter/UploadTokens/
I went to iTunesConnect and clicked on "My Apps", what I saw a message that "Can not connect... please contact Apple".
Here I don't know why it suddenly stops working!
I submitted the same build which was there on iTunesConnect for submission but it has shown as processing.
After submission of that build, iTunesConnect works fine! Also, I am able to see last uploaded build in a list for submission.
In my case (I am using OSX Catalina), I was not able to find the folder:
Library/Caches/com.apple.amp.itmstransporter/UploadTokens/
Under my user home directory (even when showing hidden files and folders)
but it seems my problem was a bit different and I just closed xCode completely (every xCode window opened) and reopened it again then I archived my project and uploaded it without any issues
maybe this could help someone else fix this issue
You need to clear out the upload tokens that are "stuck". To do this, open the tokens file found in /users//.itmstransporter/UploadTokens/. You should see one line of text at the top that refers to your current upload token. Simply delete this line and save the file. You should now be able to submit your app again.
Cheers