whenever I add an Android project to a git repository using the eclipse plugin EGit I get this Error message
Failed to initialize Git team provider.
when visualising the error log I get this :
Failed to initialize Git team provider.
Problems encountered while moving resources.
Could not move '/SearchInContatsWithLoader'.
Could not move: D:\AndrComp\SearchInContatsWithLoader.
Problems encountered while deleting files.
Could not delete: D:\AndrComp\SearchInContatsWithLoader\libs\android-support-v4.jar.
Could not delete: D:\AndrComp\SearchInContatsWithLoader\libs.
Could not delete: D:\AndrComp\SearchInContatsWithLoader.
Check if you don't have a windows process blocking those file (keeping an handle on them), which would prevent another process (like EGit) to move them.
To solve the issue, try to close as many processes as you can (or, even better, reboot and launch just Eclipse), and try again your operation.
Related
I have an issue when building project after created a new project in different volumes in Mac Os.
This what error said :
Could not create service of type DefaultGeneralCompileCaches using GradleScopeCompileServices.createGeneralCompileCaches().
> Timeout waiting to lock Java compile cache (/Volumes/SDMICRO/ANDROID/AwPlayerTes/.gradle/7.0.2/javaCompile). It is currently in use by another Gradle instance.
Owner PID: unknown
Our PID: 2394
Owner Operation: unknown
Our operation:
Lock file: /Volumes/SDMICRO/ANDROID/AwPlayerTes/.gradle/7.0.2/javaCompile/javaCompile.lock
Actually this is not my true directory in development project. But i have no choices because of run out of space. But this project are failure build. I have tried some solution like this. But none of them are works, FYI i use Mac and Android Studio Archtic Fox.
Please someone help me
please try to delete the Lock file, and then rebuild the project.
I encoutered the same problem and already solved it.
I try to build apk file in my tfs server. When i run build, after 5 minutes tfs server tell me that my apk file was build and status ok, byt in folder not apk file , in folder only my logs.
Run build_APK.bat
F:\Android\projects\Mrdoc\TeamBuildTypes\mobile_v3R\\build_APK.bat "\\tfb\storage\mobile v3r_1.7\"
Get last version in TFS Server...
Unable to determine the workspace. You may be able to correct this by running 'tf workspaces /collection:TeamProjectCollectionUrl'.
Enviroment initializing...
The system cannot find the path specified.
Assembling...
Deploing path:"\\tfbd\storage\mobile v3r_1.7\"
The command "F:\Android\projects\Mrdoc\TeamBuildTypes\EOSmobile_v3R\\build_APK.bat "\\tfb\storage\mobile v3r_1.7\"" exited with code 1.
I ran the command 'tf workspaces /collection:TeamProjectCollectionUrl'
and I saw all users but it did not help me.
Overall Build Process
Get the Build
Update Build Number
Run On Agent Default Agent - test1
Get the Build Directory
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Run TfsBuild for Configuration Folder
Getting sources
Labeling sources
Generating list of changesets and updating work items
Выполнена сборка $/Doc/TeamBuildTypes/mobile_v3R/TFSBuild.proj для целевых объектов CompileConfiguration.
MSBuild Log File
If CompilationStatus = Unknown
Set CompilationStatus to Succeeded
If TestStatus = Unknown
Set TestStatus to Succeeded
First if your build service was registered with network service. Give a try with changing it to a windows user with enough build permission.
Moreover, please make sure you have a workspace mapping for your build computer and for the windows account under which build agent runs.
Take a look at this similar issue: Team Build, fixing the "Unable to determine the workspace" error
Migrated application from 6.2 to 7.0. Server MobileFirst version: 7.0.0.00.20150312-0731
The application itself works great. When push new wlapp to server, the device see's update is available. Proceed to install update and fails.
logCat
W/PluginManager(11315): THREAD WARNING: exec() call to WLDirectUpdatePlugin.start blocked the main thread for 20ms. Plugin should use CordovaInterface.getThreadPool().
W/HardwareRenderer(11315): Attempting to initialize hardware acceleration outside of the main thread, aborting
W/PluginManager(11315): THREAD WARNING: exec() call to WLDirectUpdatePlugin.showProgressDialog blocked the main thread for 44ms. Plugin should use CordovaInterface.getThreadPool().
E/com.worklight.androidgap.directupdate.WLDirectUpdateDownloader( 9466): WLDirectUpdateDownloader.validateZipFileIntegrity in WLDirectUpdateDownloader.java:129 :: Invalid direct update zip file, original file might have been altered or replaced.
7.0.0.00.20150312-0731 is an awfully old build of MFPF 7.0; many fixes, including to Direct Update took place since.
I suggest that you will update to latest available iFix from IBM Fix Central to confirm this issue still happens to you.
This is an issue in which the content type of returned direct update zip is not "application/zip" as it should be.
Note that Worklight server returns "application/zip" content type for android direct update. We have a test fix right now where we just log the different content type and continue the direct update process since it can be correct zip and content type can be changed by firewall for example.
If you create a PMR, we can give you a test fix to test (just drop worklight-android.jar into Android project -> deploy onto device). Once we confirm that it works we can deliver it to production builds. When submitting the PMR please link them to this StackOverflow question to give full background of issue.
Earlier I was attempting to remove a commit from my commit history, and went through some stackoverflow threads doing stuff like rebasing etc.
Now here I am attempting to push a new commit, but I get this error which I feel is because of what I did earlier.
Error rebasing
fatal: update_ref failed for ref 'refs/heads/master': cannot lock ref 'refs/heads/master': ref refs/heads/master is at 9529c90e148e9b2620db0f366587312e75d507b6 but expected 808b9dfbc4141d16a29fadb4bd8171c6fe8f4914
Yes, you need to rebase first and then submit the checklist, currently the local and remote are at different level.
Just save your changed files, in some tmp directory, do the rebase(Menu->VCS->GIT->Rebase).
Once origin and remote are at same level, you may manually copy these files from temp, which will be shown in version control section of android studio. You can rightclick changelist and commit and push.
Regards
Ashish
When I try update my Android Sudio I get this message:
Temp. directory: C:\Users\Rick\AppData\Local\Temp\
+----------------
| A file operation failed.
| This might be due to a file being locked by another
| application. Please try closing any application
| that uses the files being updated then press 'Retry'.
+----------------
com.intellij.updater.RetryException: Cannot delete file C:\Users\Rick\AppData\Local\Android\android-studio\plugins\gradle\lib\gradle-tooling-extension-impl.jar
at com.intellij.updater.BaseUpdateAction.replaceUpdated(BaseUpdateAction.java:40)
at com.intellij.updater.UpdateZipAction.doApply(UpdateZipAction.java:199)
at com.intellij.updater.PatchAction.apply(PatchAction.java:140)
at com.intellij.updater.Patch$3.forEach(Patch.java:198)
at com.intellij.updater.Patch.forEach(Patch.java:248)
at com.intellij.updater.Patch.apply(Patch.java:194)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:86)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:77)
at com.intellij.updater.Runner.doInstallImpl(Runner.java:307)
at com.intellij.updater.Runner.doInstall(Runner.java:268)
at com.intellij.updater.Runner.access$000(Runner.java:18)
at com.intellij.updater.Runner$2.execute(Runner.java:258)
at com.intellij.updater.SwingUpdaterUI$7.run(SwingUpdaterUI.java:230)
at java.lang.Thread.run(Thread.java:745)
The file Android\android-studio\plugins\gradle\lib\gradle-tooling-extension-impl.jar is probably in use by some JVM process (shown as java.exe in Task Manager).
Solution that worked for me was to close the updater and close all java.exe processes in Task Manager, then open Android Studio and try updating once more. This time the update should go all the way through.
A workaround:
1-Close Android Studio.
2-Right-click "Android Studio" icon and select "Run as administrator".
3-Go to "Help->Check for Update..."
There is no way for updating anything without the rule of updater. And the rule must be administrator or super user.
P.S.
As how it's name, updating is updating, renewing or deleting. Then it knows what it takes.
I was getting the exact error you getting. I left my PC on over night and clicked retry and it worked. Very strange. I also tried using:
handle - http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
and
Process explorer - http://technet.microsoft.com/en-us/sysinternals/bb896653
to check what is locking that file and they both showed nothing. That is when I clicked retry and it worked