This is indeed a caching problem. You can bust the cache by adding a random number to the URI's query string. Someone has already done that for you:
https://github.com/bertramdev/angular-cachebuster Raul On Apr 30, 2014, at 6:49 AM, cutey Love <[email protected]> wrote: > Must be some kind of cache issue? but does anyone know a fix? > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
