{"action":"created","issue":{"url":"https://api.github.com/repos/linnovate/mean/issues/1219","labels_url":"https://api.github.com/repos/linnovate/mean/issues/1219/labels{/name}","comments_url":"https://api.github.com/repos/linnovate/mean/issues/1219/comments","events_url":"https://api.github.com/repos/linnovate/mean/issues/1219/events","html_url":"https://github.com/linnovate/mean/issues/1219","id":88829474,"number":1219,"title":"States are sometimes unable to resolve","user":{"login":"rjVapes","id":1992658,"avatar_url":"https://avatars.githubusercontent.com/u/1992658?v=3","gravatar_id":"","url":"https://api.github.com/users/rjVapes","html_url":"https://github.com/rjVapes","followers_url":"https://api.github.com/users/rjVapes/followers","following_url":"https://api.github.com/users/rjVapes/following{/other_user}","gists_url":"https://api.github.com/users/rjVapes/gists{/gist_id}","starred_url":"https://api.github.com/users/rjVapes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rjVapes/subscriptions","organizations_url":"https://api.github.com/users/rjVapes/orgs","repos_url":"https://api.github.com/users/rjVapes/repos","events_url":"https://api.github.com/users/rjVapes/events{/privacy}","received_events_url":"https://api.github.com/users/rjVapes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-16T20:16:48Z","updated_at":"2015-06-18T18:19:55Z","closed_at":null,"body":"When reloading the site, sometimes links/states will result in a message like:\r\nError: Could not resolve 'myLink' from state 'home'\r\n\r\nWithout changing any code, reloading (sometimes multiple times) can solve this.  If you try to directly visit the route, like /myLink in the example, it would kick you to the homepage.  If you have a menu link that points there, you'll have a text editing cursor (instead of pointer) and you'll get that error upon clicking.\r\n\r\nI think this same error was present in the mean.io presentation @liorkesos gave, as it had the same behavior and clicking the link resulted in an error in the console.\r\n\r\nhttps://youtu.be/oUtWtSF_VNY?t=32m20s\r\n\r\nI can't reliably reproduce, and because of the nature I wonder if it's a matter of dependencies loading in a certain order."},"comment":{"url":"https://api.github.com/repos/linnovate/mean/issues/comments/113246496","html_url":"https://github.com/linnovate/mean/issues/1219#issuecomment-113246496","issue_url":"https://api.github.com/repos/linnovate/mean/issues/1219","id":113246496,"user":{"login":"rjVapes","id":1992658,"avatar_url":"https://avatars.githubusercontent.com/u/1992658?v=3","gravatar_id":"","url":"https://api.github.com/users/rjVapes","html_url":"https://github.com/rjVapes","followers_url":"https://api.github.com/users/rjVapes/followers","following_url":"https://api.github.com/users/rjVapes/following{/other_user}","gists_url":"https://api.github.com/users/rjVapes/gists{/gist_id}","starred_url":"https://api.github.com/users/rjVapes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rjVapes/subscriptions","organizations_url":"https://api.github.com/users/rjVapes/orgs","repos_url":"https://api.github.com/users/rjVapes/repos","events_url":"https://api.github.com/users/rjVapes/events{/privacy}","received_events_url":"https://api.github.com/users/rjVapes/received_events","type":"User","site_admin":false},"created_at":"2015-06-18T18:19:55Z","updated_at":"2015-06-18T18:19:55Z","body":"After some debugging I can add that when this problem occurs, the public/routes/myPackage.js's module.config is not loaded.  Specifically if I have:\r\n\r\n```\r\nconsole.log(\"Loading Releases Config\");\r\nangular.module('mean.gd-releases').config(['$stateProvider',\r\n  function($stateProvider) {\r\n    \r\n    console.log(\"Loading Releases Routes\");\r\n...}\r\n```\r\n\r\nWhen the bug occurs, I'll see the first log message, but not the second.  I don't receive any other errors, so open to ideas as to why the route file would be loaded but the config would never be called."}}