-
26 Apr 2012 8:53 AM #21
@zombeerose
I found using the create jsb pointed to a URL was the simplest.
I've had the sencha create jsb working with my stuff with beta 1 and 2 as well as 1.2.3 version of Sencha command sdk tools.
I'll find the post where I talk in more detail about it.
http://www.sencha.com/forum/showthre...l=1#post763129
-
26 Apr 2012 8:54 AM #22
-
27 Apr 2012 3:00 AM #23
inside my .senchasdk is just on line:
sdk
You can create such file in app folder and sencha command will work fine.
-
28 Apr 2012 8:53 AM #24
RESOLVED
RESOLVED
create a file called ".senchasdk" in your sdk folder with the value of "." meaning that this folder is an sdk folder.
my paths are:
/Projects/SenchaTouch2/SDK/ -- I put the .senchasdk file in here
/Applications/SenchaSDKTools-2.0.0-beta3/
--Hope this helps
-
12 May 2012 8:00 PM #25
I have the same issue. The problem is the result of a unclear installation guide. Basically, you need to
- install the SDK Tools. The current version is Beta 2.0.0 Beta3. The path should be in your Path environment. In windows, the installer takes care of it.
- download the Sencha Touch 2.0.1 zip file. This is the SDK. Unzip it to a folder, for example C:\sencha-touch-2.0.1
- Then run cmd and change path to C:\sencha-touch-2.0.1. Make sure the SDK Tools path is in the Path.
- run sencha. Now it should display 'Sencha Command v2.0.2'
-
25 May 2012 6:03 AM #26
SOLVED with MAC
SOLVED with MAC
I solved this problem on my mac like this:
Identify the folder of the SDK. In my mac is \Developer\SDKs
Download the free Sencha Touch 2 SDK and SDK Tools from the Sencha website.
Start the installation of SDK Tools and when the installation asks for the install path, choose \Developer\SDKs .
Extract the Sencha Touch 2 SDK zip file in the folder \Developer\SDKs
Open a line commad and go to the path \Developer\SDKs
Try now the command "sencha" or "sencha generate app GS ../GS"
In my mac works good.
-
5 Jul 2012 2:01 PM #27
-
14 Jul 2012 10:46 AM #28
you need to have a file called .senchsdk for the sencha command to work
the sencha command looks for this file to determine its actions..
i created a secha project, move it around and the sencha command started giving the error u have mentioned. this happened because .senchsdk was a hidden file and was never copied around
Solution is simple. In your sencha project folder create a file called .senchasdk
its content should be: sdk
thats it. now u r set. and the command should work.
PS: its content is the path to the directory where sencha sdk is. by default that should be sdk
-
24 Jul 2012 4:56 PM #29
Ugh, I keep getting this problem as well, I've tried some of these fixes but I have not tried the .senchsdk yet. The issue I am having though is the path issue but it said the build and sign is successful. I'm launching the packaging function from the Architect tool though. I don't know how much of a difference that makes. I'm using the latest version of Architect, SDK and SDK Tools. I get the app create but it throws that error. It however runs in the simulator and I can add it to iTunes but when I try to put it on my device either with iTunes or Xcode, I get install errors. I've literally been racking my brain on this all day. I've got my device set up in the provisioning portal, I've got my cert, I've got my App ID, etc..
I actually moved the SDK into the /red directory to try that. My app wound up being 187 mb and all it is, is a red screen. That's all I tried to test this with.
cd /Users/ashapiro75/Documents/SenchaProjects/red/
sencha package packager.json
[ERROR] The current working directory (/Users/ashapiro75/Documents/SenchaProjects/red) is not a recognized Sencha SDK or application folder
The application was successfully packaged
The application was successfuly signed
logout
So I take the .app that it creates, I put it into iTunes, try to add it to my device and I get an error... I'm about to give up on Sencha, it seems every time I get something down, something else changes and I feel like I am chasing my tail.
-
11 Aug 2012 3:28 AM #30
I've found a solution in Mac
I've found a solution in Mac
All the trouble seems to be related to that .senchasdk file at the root of the SDK folder.
In order to make sure that the file is there:
- use the downloaded folder of the SDK as it is -> don't try to copy its contents into a different folder. I've done that and the dammed .senchasdk is not copied.
Once you launch the "sencha" command from the SDK folder, everything works fine.
Hope it helps,
Fernando
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote