Cannot create a new project with ionic - ionic-framework

I've seen this problem on stack overflow few days ago, and the next day I have it too.
I am unable to create a new ionic project with cordova.
When the prompt ask me if I want to integrate cordova with the app and whatever my answer was (Yes or no), I have to wait hours and hours and nothing happens and just a folder with just single file (src) is created.
I am using the latest version of Node and NPM.
I tried to uninstall everything globally and re-install it again, but still having the same problem.
Any help would be appreciated. I can't provide any more details as this is what I got. I tried everything from removing/uninstalling all and then re-install. Restart computer, even change it. The internet speed is good (I don't think it has something to do with it).
Update
I tried to add --no-git to the command and still doing the same thing:
ionic start proj tabs --no-git

Try with a --no-git. At least this helped this guy: github issue

Related

I'm struggling with eclipse, error in appcompat

I'm new to android, the last few days I've been struggling with eclipse, sdk. My friend sent me a code and I want to run it in my mac computer. Please can you tell me what software I have to use and how. I'm struggling with app compat error. Please can you tell me the step by step process to run the code in eclipse, like which versions I have to use. Please help me.
First of all go to the properties-android - and remove redcrossed appcompact library and just download appcompact library and import it in your worspace ;
then add it in your project. then refresh the project clean it and it will work

Adding Native support to gstreamer tutorial won't finish

I'm following this:
http://docs.gstreamer.com/display/GstSDK/Installing+for+Android+development
I'm using the Windows x86 ADT bundle, the Windows x86 r9d NDK, and the Gstreamer SDK linked to in the guide.
I was able to get the first tutorial to add native support, build, and run. Then I tried the 3rd tutorial, and Eclipse becomes unresponsive. Same thing happened with the 2nd tutorial. I left it to do it over the weekend in case it just took a long time. When I change anything for another attempt I delete the tutorial folder completely and use a fresh copy from the zip file. I have also remove the ADT bundle completely and started over from scratch.
If I cancel, I have the expected build errors of missing import com.gstreamer.GStreamer;
The GSTREAMER_SDK_ROOT_ANDROID value is set to C:/gstreamer
The NDK Location is C:\android-ndk-r8d
I switched to using r8d as recommended in: Adding Gstreamer support to an android NDK project
One comment also suggests adding to the gstreamer.mk file:
ifndef SYSROOT
SYSROOT := $(NDK_PLATFORMS_ROOT)/$(TARGET_PLATFORM)/arch-$(TARGET_ARCH)
endif
I attempted this but there is a gstreamer_prebuilt.mk file it may be using instead.
My only clue is that Tutorial 1 does not use gstreamer plugins and the tutorials that do not work use plugins.
Thank you for any help you can give.
Edit: I tried using android-ndk-r7c also.
Then I deleted the ADT bundle and tried going the "Use an existing IDE" route, same result.
I'm going to try a different machine, and also see if I can compile it without eclipse, but I would love to hear any guess on what's going on.
Edit2: I watched a youtube video of someone setting this up (as far as I can tell he adds the NDK manually adding a build program and pointing to the ndk-build.cmd file):
https://www.youtube.com/watch?v=nKfAELFdf9A
This seemed to work but I was still missing import com.gstreamer.GStreamer; so I closed the tutorial 2 project, built and ran tutorial 1, opened tutorial 2 again, cleaned, built, and it ran.
Problem solved.
I watched a youtube video of someone setting this up (as far as I can tell he adds the NDK manually adding a build program and pointing to the ndk-build.cmd file):
https://www.youtube.com/watch?v=nKfAELFdf9A
This seemed to work but I was still missing import com.gstreamer.GStreamer; so I closed the tutorial 2 project, built and ran tutorial 1, opened tutorial 2 again, cleaned, built, and it ran.
Problem solved.

Netbeans only slow when copying and pasting?

My Netbeans has been insanely fast for over 2 years, until this morning. Something strange, however, is now happening. Every time i press "copy and paste" ... so CTRL-C, it goes slow. This is what I see:
So, the moment I press CTRL-C, that shows in the bottom, my entire machines goes into super slow mode, and then 5 seconds later it stops.
I've considered maybe there's a keylogger on my machine, but can't find anything. And it's only slow when I copy and paste from Netbeans, nothing else. Maybe Netbeans is sending data out some other way?
Any ideas why Netbeans would just go slow like this?
UPDATE
I only have one project open
I've disabled the git and subversion plugins
I am working on a Laravel project
It's slow when I copy from a VIEW or when I copy from a CONTROLLER (I know css files often go a bit slow because of Parsing, so I figured mentioning this is probably worthwhile)
I followed the advice at the end of this article: here and uninstalled "BlueStacks". Problem solved.
UPDATE
Just in case the article gets deleted, here is the advice the user gives on that page:
I meet the same problem. When I copy a word in the IDE, the IDE does not response until 2 or 3 seconds. I did not confront this problem until few days ago. I try to use the latest netbeans and the latest jdk, but that does not work. Then I find someone said http://bugs.java.com/bugdatabase/view_bug.do?bug_id=5078787 is the problem. And the problem is somewhat about the COM in windows. So I try to install the netbeans to another Win7 PC, and the problem is gone. In that case, I guess the problem is not the netbeans, but some other application in windows. Later I uninstall some of the application I just installed few days ago. And the IDE works right now. The applications I uninstalled is "imc studio" "imc license manager" and "blueStacks" an android simulator. I guess these application may have influence to the COM of Win7. Hope my solution will help to this bug.
You can also just stop the BlueStacks Agent process from Task Manager while you're using NetBeans.

How to diagnose metro app deployment errors?

When trying to debug a Metro project from VS, I came across this error:
DEP0700 : Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is PACKAGENAME and it was published by CN=some Guid. (0x80073cf9)
But I have already uninstalled the app from the Start page, also, I can confirm that there is no entry left in Add/Remove program.
And since the access to the "%PROGRAMFILES%\WindowsApps" folder where the app files reside in is blocked, so I have no way to see if the app is still there.
However, I can still find many 'PACKAGENAME' occurances in the registry.
How to diagnose this? How to get rid of the "packaged version" so I can start debugging from VS?
Try installing the app from the windows store again, and then uninstall it from the start page. It appears that when Visual Studio does the uninstall it doesn't do it right.
1) Go to your Package.appxmanifest file in your solution
2) Go to the identity tag.
<Identity Name="xxxxxxx-yyyy-zzzz-tttt-bbbbbbbbbbbbb"
Publisher="CN=bigbob"
Version="1.0.0.0" />
3) Change the value of the Identity Name (Ex from ...bbbbb to ...bbbbc)
4) Rebuild and run
Source:
http://www.sempf.net/post/MetroUIAnother-user-has-already-installed-an-unpackaged-version-of-this-application.aspx
Are you sure you didn't just unpin the app? Try doing a search for it and see if it is still there.
I find a solution to the problem. It's said it is a "staged package" that does not show up in my start page so I can not uninstall it in normal way. I follow the steps, and successfully get rid of that "un-uninstallable" :) package.
This blog post was helpful, although after an hour or so of troubleshooting it turns out that I had indeed installed the package under another user account. After switching accounts and uninstalling from the start screen it worked fine.

Xcode upgrade: PBXContainerItemProxy missing containerPortal key

I just upgraded my Xcode, now when I try to open my project, I get this error:
Project /Users/xxx/xxxx/xxxxx/xxxxxx/xxxxxxxx.xcodeproj cannot be opened: PBXContainerItemProxy (xxxxxxxxxxxxxxxxx) is missing a containerPortal key
I have searched the web and stackoverflow, but cannot get anything relevent to come up at all regarding this.
I do have Three20 as part of my project, I don't know if that matters. I just upgraded to xcode 4.4.1
Thanks for any insight.
-D
the project icon which we see i.e projectname.xcodeproj, is actually a directory, you do this
1. in terminal do cd yourproject.xcodeproj
2.ls
3.vi project.pbxproj
4. scroll down till /* Begin PBXContainerItemProxy section */
5.there you will see all sections check for the section which is missing a portal key edit it and save it :wq it will work
in image if you see the first section is missing container portal key.just pic it from other section and replace it..
it will work :D see this link
Now I should start with that I do not know the actual error, never seen it before, but I did find a reference to a "PBXContainerProxy"-error in this post (As soon as I add a project to XCode 4.0.2 it crashes) and thought you might try the solutions from there?
"Apparently this is due to the new version of XCodeProjects. I found a
work around by pre-compiling the library that was causing the issue
and then using the linker to link to the .a file. I also had to copy
the .a library into the DerivedData path.
The real solution was to remove the project and replace it with an
updated project for the new version of XCode."
Hope that helps somewhat :)
Never saw that error either, but if you're upgrading directly from XCode 3.X I'd suggest you to go to https://developer.apple.com/downloads/index.action?name=Xcode
and download/install a previous version of Xcode somewhere else. (You can have several different copies installed on your machine, just google it if you don't know how but just remember to use xcode-select to pick the one you want to use). Repeat with all the versions back to 4.0.1 until (hopefully) it works. I know it's tedious but it might help.
If it does, validate the project settings and try to open it with 4.4.1. That should work.
Good luck