I'm migrating from Nexus 1.9 to 2.7 to 2.10 and was able to fix all issues apart from uploading artifacts to Nexus. When I'm selecting the pom.xml file and artifact, UIs shows me the progress bar and never ends. No errors in log files. I checked the permissions and all configurations with the previous version of Nexus, don't see any difference.
By the way it happens only with zip artifacts.
Any ideas, what can be wrong?
Related
When I do symfony self-update I get the following error - how can I solve it?
Backup failed, rename D:\SERVER\Symfony\symfony.exe C:\Users\FairyWilbury\.symfo
ny\autoupdate\2019-07-19_14-57-14-79024bb-old: The system cannot move the file t
o a different disk drive.. Canceling upgrade.
UPD.
I have just realized that the latest symfony version seems to be 4.3 with 4.4 due to release in November https://symfony.com/roadmap/4.4
Yet whenever I run symfony new --full %projectName% it suggests I should update to 4.6 (and then fails to update as described above). Screenshot of the command line: What can this problem be?
First of all, you're mixing up Symfony Local Web Server and the Symfony PHP framework. You can use the web server, which is a single executable command line developer tool, to start a new Symfony-based project or start a local server that makes your web application available for testing and debugging while you develop it. The framework, on the other hand, is the code base you build web application on.
When you run
symfony self-update
from the command line, you (try to) update the web server, not the framework.
The latest version of the web server, at the time of writing, is 4.12.10, while the framework is at 5.0.5 (or 4.4.5), so, as you can see, they're completely independent from each other.
Back to the original problem, and I was struggling with this as well, the catch is that we both use Windows and installed the web server (symfony.exe) to a folder in drive D: (in your case it's D:\SERVER\Symfony). While it's running, it stores config and other files in a ".symfony" directory in the folder of your Windows user account (C:\Users\FairyWilbury). And during the self-update process, that's where it tries to move the original symfony.exe file. For some unknown reason, it cannot do that between different drives, not even in an Administrator-privileged command line window.
Strange, as it is, the only solution I found was the following.
I created a TEMP folder on drive C:
Copied symfony.exe from its folder on drive D: to C:\TEMP
Opened up command line, and switched the current dir to C:\TEMP
Ran symfony self-update -- this time it went smoothly
Closed the command line window
Moved the new symfony.exe file from C:\TEMP to the folder on drive D:
Removed C:\TEMP folder
I know it's a bit cumbersome, but we have to consider that Windows is not the most popular development platform for PHP applications. ;)
okay, look, in this case, I dont really find anything about this symfony self-update stuff, so...
In the version title the third part (so the 1 in 4.6.1) is a patch, what that only contains bug fixes, so you need the latest minor version first 4.6.0.
Basicly you need follow this doc:
symfony/doc/upgrade_patch.html
And, as it starts above, first you need follow this doc (attentively):
symfony/doc/4.2/upgrade_minor.html
This upgrade_minor.html writes: The composer.json file is configured to allow Symfony packages to be upgraded to patch versions., so ...
This command helped me to update symfony binary:
sudo symfony self-update
I use ant to build flex application and sign it with self generated certificate, it works fine for a long time with "Flex 4.6 & AIR 3.5"
Today I've tried the latest SDK "Flex 4.10 & AIR 3.9" but my build script doesn't work on OSX because of some problems with certificate:
[INFO] [org.gradle.api.internal.project.ant.AntLoggingAdapter] [ant:java] Packaging failed. Make sure your computer time is in sync and your certificate is valid
In the same time it works with latest SDK on Windows.
I've tried to generate new certificate or use another OSX but result still the same.
I received the same problem when I had 450MB video files included the project. The problem was the file size was too big. I left the video files out of the project and could successfully publish it. Then I put the video files into the project folders manually.
Apparently, this is a known issue with the AIR SDK. I don't know why or how it suddenly stopped working for people, but the fix is to remove the section from air app descriptor .xml file.
See this link for more info, and perhaps a heads-up when Adobe fix the problem for real.
http://forums.adobe.com/thread/1317862#5771096
I have created a Cordova 2.1.0 app, It ran fine for the first 2-3 times. But now when I am trying to run it through terminal it is giving me the following error.I didn't change anything.
Ankurs-Mac-mini:~ ankur$ /Users/ankur/Desktop/CordovaSMS/cordova/emulate
Ankurs-Mac-mini:~ ankur$ 2012-10-17 16:11:08.695 ios-sim[7032:507] stderrPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
2012-10-17 16:11:08.698 ios-sim[7032:507] stdoutPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
[DEBUG] Session could not be started: Error Domain=DTiPhoneSimulatorErrorDomain
Code=1 "iOS Simulator failed to install the application." UserInfo=0x7fc643902320
{NSLocalizedDescription=iOS Simulator failed to install the application.,
DTiPhoneSimulatorUnderlyingErrorCodeKey=-1}
any help would be appreciated.
Thanks
Solved the problem
Deleting contents of ~/Library/Application Support/iPhone Simulator and re-run the project solved this problem.
or you can simply reset content and setting of the simulator.
Try manually launch the iOS Simulator and from the "iOS Simulator" menu, click "Reset content and settings", then close and rebuild your app.
My solution is:
From menu, iOS Simulator, Reset Content and Settings.
Close XCode 5.0: close project and close it from Dock and re-open the project and launch again, like in Windows :)
I tried everything mentioned above and nothing worked. My problem was iOS 7 specific. I was finally able to resolve the issue by assigning a non-empty value to Bundle versions string, short (CFBundleShortVersionString) in the -Info.plist file. Looks like iOS 7 doesn't like an empty value for the build number. I had a script that auto increments the bundle number by 1 every time I build the project so this field was empty. I just assigned a dummy value there to get it working.
You can also remove the app from the simulator.
This worked for me in iOS6.1
Solved here: https://stackoverflow.com/a/16279286/1927253
I copied a folder into XCode 4.6.2 with the name "Resources". When XCode asked, I created the folder references for any added folders.
Every time I did this, I would have to goto the Derived applications directory, and delete the build directory for my project to get it working again.
Solution: Do not copy a folder by reference into XCode with the name "Resources". Rename it to something else other than Resources.
Very annoying error.
just reset your simulator and re-run your project
Unfortunately none of these solutions solved my problem. I did everything, even restarting my mac but it was still failing. What actually did solve my problem was to go to the Organizer and delete the Derived Data and Snapshots.
Had the same problem after installing XCode 5. Had no iOS 6.1 Sim or SDK. Obtained these. Tried to run the App up under the iOS6.1 Sim and go the failed to install message. Having read through all of the above posts, I decided to simply remove the App from the Simulator and re-istall, re-run from the project window and that solved it for me.
I tried ALL these things and more including reinstalling Xcode 5 and nuking every xcode and simulator preference/application support file with no luck.
Then for the hell of it, I CHANGED my short bundle version string (it already had a value, it was not empty), and it fired right up.
3 hours gone but yeah
All the answers I looked for do not work for me!.
Finally
The only way to make it work is as follows
1.Check the version of titanium being used for the project in tiapp.xml
2.right click the prject in the project explorer window.
3.Select Properties
4.Choose project build path. Select Titanium Mobile SDk all versions of 3.* Tick all of them.
5.Now click apply and re run the project.
None of the above worked for me, I finally compared my info.plist to another project and found that I had somehow deleted the "Executable File = ${EXECUTABLE_NAME}" key/value pair, replacing it fixed the problem for me.
This error occurs on iOS 7.0 if you leave the "Build" empty.
Enter a build number!
What worked for me was to simply delete an old version of the app, which was made in a prior version of Xcode (likely 4, now running 5) from the simulator (tap-hold, jiggle, x).
I encountered this problem while trying to create a build for Facebook application approval. I found that for some reason, when I used the following command line:
xcodebuild -arch i386 -sdk iphonesimulator7.1 -scheme Mana -configuration Release
the files didn't end up in [project root]/build/... (as the instructions on Facebook suggest), but in ~/Library/Developer/Xcode/DerivedData/[app name + unique identifier]/Build/Products.
I'm not sure exactly what's going on here (anyone who knows more please enlighten me!) but I was able to run the files in the DerivedData directory on the simulator. Hopefully they'll also work for Facebook!
I tried everything mentioned above and nothing worked.
Finally the only way to make it work was unsetting DYLD_INSERT_LIBRARIES=/usr/lib/libimckit.dylib
How I did this:
Open terminal and typing "sudo vi /etc/launchd.conf"
Changing
"setenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
to
"unsetenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
Save changes
Reboot your system
In this post [1] explain what DYLD_INSERT_LIBRARIES is for
[1] https://stackoverflow.com/a/26053165/2091181
On Mavericks 10.9.5 using Xcode Version 6.0.1 (6A317) with an iOS SDK supporting 8.0 originally had Simulators all version 8 all getting this error. All the advice above was not working for me. So went to Xcode->Preferences->Downloads and saw as installable (but not yot installed) in the Components section were iOS Simulators 7.1 and/or 7.0. Went ahead and installed the 7.1 Simulators and got extra designations on the Product->Destination list Simulators of version 8.0 and 7.1, and using the 8.0 still had the same error, but the 7.1 Simulators all worked.
When I try to debug or run my flex application it shows "Out of memory" dialog.
I use IDEA 11.1 Ultimate and Windows 7 64x.
What I tried:
creating a new blank project and running it - same result (Out of
memory)
using 64x version of IDEA - didn't help
increasing xmx setting up to 6Gb - same result
installing IDEA 10.5 and launching my project there - it works fine. But I really need 11.1 to run my
project.
uninstalling and reinstalling JRE and JDK versions 7 and 6 (not at the same time ofc) -
didn't help
switching from flex SDK 4.6 to 4.5 - didn't help
reinstalling IDEA 11.1 with all the settings wiped out - didn't help!
It used to work fine before. I have no idea what could have changed.
I noticed that compilation works fine - I get a proper compiled swf file of my project that can be run in flashplayer. But right at the moment when IDEA is supposed to run the newly compiled swf it eats up all the memory.
What can be done about it? What else should I try?
I really don't understand why reinstalling IDEA didn't solve my problem. May be I didn't wipe out all settings?
Try File | Invalidate Caches or even run with all the defaults after renaming IDEA folders.
There were also some related fixes in IDEA 11.1.3 version, give it a try.
If it doesn't help, upload hprof memory dump to JetBrains FTP server and contact support for help, see http://devnet.jetbrains.net/docs/DOC-192 (Memory Snapshot section at the bottom) for details. You need to run IDEA with -XX:+HeapDumpOnOutOfMemoryError option.
Did you open more IDEA windows? Like opening another project into new window. In such case closing the other window will not release memory. The only thing that helps me is to restart the whole IDEA application.
I created an empty Single View application using Xcode 4.2 on OSX Lion 10.7.2 targeting iPhone 5. The project built happily however when launching the simulator I receive the following error message:
iOS Simulator could not find the SDK. The SDK may need to be reinstalled.
I then tried targeting the iPad with the same results. I removed Xcode using the terminal and downloaded a fresh copy from the AppStore. The clean installation generates the exact same error.
It seems that the SDK is not being deployed during installation. Any advice or tips on how I can correctly install the iOS 5 SDK for the simulator to work?
Update
I downloaded the iOS 4.3 simulator which was not installed. The simulator works perfectly if I select the 4.3 SDK but for some reason is not recognizing the folder containing the 5.0 SDK.
Update
I reformatted the MacBook, reloaded a clean OSX Lion without restoring any backups and installed Xcode. Running the simulator directly after the installed worked, however after a reboot and relaunching Xcode the error came back. The SDK itself seems to have been corrupted. Will try and reinstall Xcode again.
After some testing it turns out the problem is caused by a 3rd Party Software. Recently the developer of TotalFinder removed the Asepsis portion of the system and created a separate application for the handling of DS_Store files.
Unfortunately, this breaks the iOS Simulator once installed, and even after uninstalling Asepsis, I needed to rebuild my whole machine to get rid of the error.
Update
BinaryAge is aware of the issue with regards to Xcode 4.2 and it is now listed on the know issues page and a warning banner displayed on the download link.
Final Update
It seems BinaryAge has changed the way Asepsis works and this is no longer an issue with the latest versions.
Did you try "File -> Reset Content and Settings ..." in the simulator ? I also encountered the similar problem, but it worked after I reset the simulator! In fact, I also found it worked after I removed all the existing projects and created new ones, but it occurred again after I restart xcode. Fortunately the "Reset" always works for me and I hope it can be helpful for your case.