Thank you for reporting this bug. We will make it our priority to review this report.
  1. 27 Jul 2011 9:30 AM #11
    zombeerose
    zombeerose is offline
    Ext JS Premium Member
    Join Date
    Mar 2008
    Location
    Phoenix, AZ
    Posts
    625
    Vote Rating
    10
    zombeerose will become famous soon enough zombeerose will become famous soon enough
      0  

    Default


    I am getting the same error
    Code:
    TypeError: 'undefined' is not an object
Line: 0
Source: undefined
    when running the SDK against Ext 4.0.5.

    My command for Ext 4.0.4 runs cleanly:
    Code:
    /cygdrive/c/PROGRAMMER/SenchaSDKTools-1.2.2/command/sencha.bat slice theme -v -d htdocs\\includes\\library\\extjs\\ext-4.0.4 -c htdocs\\includes\\library\\extjs\\my\\resources\\css\\theme.css -o htdocs\\includes\\library\\extjs\\ext-4.0.4/resources\\themes\\images\\my\\
    But the Ext 4.0.5 command fails:
    Code:
    /cygdrive/c/PROGRAMMER/SenchaSDKTools-1.2.2/command/sencha.bat slice theme -v -d htdocs\\includes\\library\\extjs\\ext-4.0.5 -c htdocs\\includes\\library\\extjs\\my\\resources\\css\\theme.css -o htdocs\\includes\\library\\extjs\\ext-4.0.5/resources\\themes\\images\\my\\
    The double backslashes are necessary.
    Reply With Quote Reply With Quote
  2. 31 Aug 2011 12:10 PM #12
    FoxMulder900
    FoxMulder900 is offline
    Sencha User
    Join Date
    Aug 2008
    Posts
    97
    Vote Rating
    4
    FoxMulder900 is on a distinguished road
      0  

    Default


    Ok, I am getting this exact same error, I have tried both the URL and just index.html. Does this mean I am missing an Ext.require somewhere? If so how do I tell where to look?

    The only warning I get in my console when my page loads is "Store defined with no model. You may have mistyped the model name." my understanding was this warning is from having a TreeStore and will supposedly be fixed in 4.1 but could it have anything to do with my build error?
    Reply With Quote Reply With Quote
  3. 31 Aug 2011 12:26 PM #13
    stevil
    stevil is offline
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Location
    Denver, CO
    Posts
    1,045
    Vote Rating
    7
    stevil will become famous soon enough
      0  

    Default


    @zombeerose,

    4.0.6 just dropped today, and fixed this problem for me.

    stevil
    Reply With Quote Reply With Quote
  4. 28 Sep 2011 11:56 AM #14
    Dehru
    Dehru is offline
    Sencha Premium Member
    Join Date
    Mar 2011
    Posts
    9
    Vote Rating
    0
    Dehru is on a distinguished road
      0  

    Default This solution solved it for us

    This solution solved it for us


    We had a few lines of javascript above the Ext.application({...}) in our app.js file. For us, this produces the error. When we removed those lines it solved our problem.
    Reply With Quote Reply With Quote
  5. 18 Oct 2011 11:56 PM #15
    jithsajith
    jithsajith is offline
    Sencha User
    Join Date
    Oct 2011
    Posts
    1
    Vote Rating
    0
    jithsajith is on a distinguished road
      0  

    Thumbs up I got the same.. And I fixed it

    I got the same.. And I fixed it


    Hiii...
    I am new to extJs. I also got the same error message Undefined is not an Object. When I checked in detail the xtype I gave was incorrect. I believe this error occurs when U gave an incorrect xtype.

    Regards
    Reply With Quote Reply With Quote
  6. 19 Oct 2011 7:29 AM #16
    Dehru
    Dehru is offline
    Sencha Premium Member
    Join Date
    Mar 2011
    Posts
    9
    Vote Rating
    0
    Dehru is on a distinguished road
      0  

    Default Often, The Error Can Be Ignored

    Often, The Error Can Be Ignored


    I have found that the error is produced when I use a static html file vs one served from http:// But the jsb3 file is fine.

    I get the error from this command:

    Code:
    sencha create jsb -a index.html -p app.jsb3

    But not this command using http://:
    Code:
    sencha create jsb -a http://localhost:9090/app/index.html -p app.jsb3

    But in both cases, the jsb3 file is fine. I didn't realize this at first...I assumed the error caused a failure to build the file.
    Reply With Quote Reply With Quote