You found a bug! We've classified it as BROW-2334 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #11
    Sencha Premium Member
    Join Date
    Jul 2008
    Posts
    19
    Vote Rating
    0
    mik977 is on a distinguished road

      0  

    Default


    Yes, I can confirm that the file cache.appcache is served with mime-type text/cache-manifest. I checked in Chrome with dev-tools. The app is reloaded ok in Chrome and asks me if I want to update the app... so in Chrome all is good. In Space however, the app is not reloaded to the new version and I am not asked to update. I am testing on Android (4.2.2).

  2. #12
    Sencha Premium Member
    Join Date
    Jul 2008
    Posts
    19
    Vote Rating
    0
    mik977 is on a distinguished road

      0  

    Default


    Hi, can you confirm there is a bug in app update (production build) or am I doing something wrong?

  3. #13
    Ext JS Premium Member
    Join Date
    Oct 2009
    Posts
    67
    Vote Rating
    3
    hhangus is on a distinguished road

      0  

    Default


    Just here to say that I am also seeing this problem. I ended up changing the url of the application just so i could keep developing.

    i'd like to add that I am including these two sencha libraries, but I only saw this problem *after* adding the space library. That doesn't mean it's the cause, but it is correlation.

    http://cdn.sencha.com/touch/sencha-t...h-all-debug.js
    http://space.sencha.io/space.js

    edit:
    The exact problem i'm seeing is that the app isn't updating even though the manifest is definitely changing. I know it's changing, and I know it's served with the correct mimetype because the app works fine in normal browsers, just not in the Space environment on my iPad2.

  4. #14
    Ext JS Premium Member
    Join Date
    Oct 2009
    Posts
    67
    Vote Rating
    3
    hhangus is on a distinguished road

      0  

    Default


    Ok, so I used Chrome to debug the issue and come to the conclusion that the only real problem with Space is that it has no way to clear a bad manifest file. Chrome/Firefox have tools menu to clear their caches including manifest files, which allows me to fix them but Space doesn't. This is a serious flaw.

    In any case, what happened is I added "http://space.sencha.io/space.js" into my application headers, thus making it part of the application. But I did not add it explicitly to the manifest file. This is apparently a no-no, you *must* specify all files in the manifest or it will be considered erroneous. The "bad" manifest was then cached and could not be updated because every time it was loaded it was refused as erroneous. Thus, no changes to the manifest could be made, thus making it impossible to fix except by manually deleting the cached files which *can't be done in Space*.

    So, the solution is simple, Space needs an option to destroy the manifest and refresh the cache from an administrative tool. I suggest adding it to the space manager online application so that developers/admins can do this remotely, but users cannot.

  5. #15
    Sencha - Management Team abe.elias's Avatar
    Join Date
    Aug 2008
    Location
    Palo Alto, CA
    Posts
    406
    Vote Rating
    5
    abe.elias is on a distinguished road

      0  

    Default


    Thanks for the investigation. I'll make sure to follow up with the dev team on this tomorrow.

  6. #16
    Sencha - Management Team abe.elias's Avatar
    Join Date
    Aug 2008
    Location
    Palo Alto, CA
    Posts
    406
    Vote Rating
    5
    abe.elias is on a distinguished road

      0  

    Default


    Thanks for the report! I have opened a bug in our bug tracker.

  7. #17
    Sencha - Desktop Packager Dev Team jarrednicholls's Avatar
    Join Date
    Mar 2007
    Location
    Frederick, MD
    Posts
    1,747
    Vote Rating
    7
    jarrednicholls will become famous soon enough jarrednicholls will become famous soon enough

      0  

    Default


    Quote Originally Posted by hhangus View Post
    Ok, so I used Chrome to debug the issue and come to the conclusion that the only real problem with Space is that it has no way to clear a bad manifest file. Chrome/Firefox have tools menu to clear their caches including manifest files, which allows me to fix them but Space doesn't. This is a serious flaw.

    In any case, what happened is I added "http://space.sencha.io/space.js" into my application headers, thus making it part of the application. But I did not add it explicitly to the manifest file. This is apparently a no-no, you *must* specify all files in the manifest or it will be considered erroneous. The "bad" manifest was then cached and could not be updated because every time it was loaded it was refused as erroneous. Thus, no changes to the manifest could be made, thus making it impossible to fix except by manually deleting the cached files which *can't be done in Space*.

    So, the solution is simple, Space needs an option to destroy the manifest and refresh the cache from an administrative tool. I suggest adding it to the space manager online application so that developers/admins can do this remotely, but users cannot.
    If you delete Space and reinstall it, is the new manifest delivered and work as expected?

  8. #18
    Ext JS Premium Member
    Join Date
    Oct 2009
    Posts
    67
    Vote Rating
    3
    hhangus is on a distinguished road

      0  

    Default


    If you delete Space and reinstall it, is the new manifest delivered and work as expected?
    Yes, deleting and re-installing Space does fix the issue. Of course, it also deletes all the app data for other shared apps so it's not really an option outside of development and debugging.

  9. #19
    Sencha - Desktop Packager Dev Team jarrednicholls's Avatar
    Join Date
    Mar 2007
    Location
    Frederick, MD
    Posts
    1,747
    Vote Rating
    7
    jarrednicholls will become famous soon enough jarrednicholls will become famous soon enough

      0  

    Default


    Quote Originally Posted by hhangus View Post
    Yes, deleting and re-installing Space does fix the issue. Of course, it also deletes all the app data for other shared apps so it's not really an option outside of development and debugging.
    Definitely not an option, of course. I just wanted to confirm that case. Thanks!

  10. #20
    Sencha Premium Member
    Join Date
    May 2013
    Posts
    41
    Vote Rating
    1
    dmifs is on a distinguished road

      0  

    Default


    So what is the best way to go with this? I have to test that the application works offline so removing the manifest file from the HTML while developing is not an option.

    thanks