facebook

cache.manifest issues

  1. MobiOne Archive
  2.  > 
  3. Getting Help – General
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #349433 Reply

    bremy
    Member

    Hello

    My app using webservices and map was working pretty well requesting data when connected. I tried to see if it could be possible to have the Map control working in an offline situation. So I was adding some googleMaps URL in the NETWORK: section in the cache.manifest file

    Since that trial each time I am now running my App in the Web simulator, I am always in a “non connected” mode. For Example the Map control is displaying this message : “Network connection is required for map initialization”, also none of my webservice calls are still working (called using $.getJSON( url, function( data ) …..)

    For sure my laptop has an internet connection full available

    Any idea on the way to fix that and having my App strill working using the Web simulator????

    Thanks

    #349439 Reply

    Hi bremy,

    Can you post a small example project that demonstrate the problem? If you want to keep data in privacy send it to support at genuitec dot com, use title mobione data from bremy

    #349448 Reply

    bremy
    Member

    Thanks Octavio

    I’m going to prepare something to send you
    Also will try to deploy on a real iphone to see if I also have the same problem

    #349453 Reply

    bremy
    Member

    Problem is now fixed
    That was due to the cache.manifest file

    To fix it
    1- I renamed cache.amnisfest to cache.manifest.save
    2- I ran my in the web simulator
    3- Then Desing Center is asking to regenerate the cache.manisfest file
    4- it is working again and all network connection are now available

    THe must surprising : cache.manisfest file regenerated is EXACTELY the same as cache.manifest.save

    But at least this is working again

    cheers

    #349458 Reply

    Hi bremy,

    HTML5 webapps will only reload an appcache manifest when its binary contents change. For example touching the manifest file will not cause result in the manifest being reloaded by its webapp. It requires at least 1 byte change in the file. I suspect that regenerating the appcache resulted in changing the file’s content. For example the specified resources may not have changed but probably additional whitespace or a comment changed.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: cache.manifest issues

You must be logged in to post in the forum log in