{"id":321,"date":"2019-04-29T16:40:45","date_gmt":"2019-04-29T16:40:45","guid":{"rendered":"https:\/\/docs.sisus.co\/power-inspector\/?p=321"},"modified":"2019-05-14T12:40:47","modified_gmt":"2019-05-14T12:40:47","slug":"type-not-found-errors","status":"publish","type":"post","link":"https:\/\/docs.sisus.co\/power-inspector\/troubleshooting\/type-not-found-errors\/","title":{"rendered":"Type Not Found Errors"},"content":{"rendered":"<p>Are you suddenly seeing <strong>errors<\/strong> in the Console originating from Power Inspector code, possibly triggered by making changes to code?<br \/>\nIn particular, are you seeing this error in your Log window:<br \/>\n\u201c<strong>error CS0246<\/strong>: The type or namespace name &#8216;x&#8217; could not be found. Are you missing an assembly reference?\u201d<br \/>\nIf so, it\u2019s possible that Unity\u2019s asset loading process has failed for some reason. To fix the issue, do the following steps:<\/p>\n<ol>\n<li>If the error messages are pointing to a specific type being missing, you can try locating and selecting the script asset that defines the missing type in the <strong>Project window<\/strong>, and selecting the menu item &#8220;<strong>Assets &gt; Reimport<\/strong>&#8220;. Wait until the import process has finished, and try clearing your Console window to see if the errors are now gone. If importing has failed for multiple script assets, you might need to repeat this step multiple times for all the errors to go away.<\/li>\n<li>If you are unable to locate the specific file(s) causing the errors, you can also reimport <strong>all <\/strong>assets. To do this, select the menu item &#8220;<strong>Assets &gt; Reimport All<\/strong>&#8220;. Please note that this might take several minutes (depending on your project size).<\/li>\n<li>If even this fails, you can try deleting the whole <a href=\"https:\/\/docs.unity3d.com\/Manual\/BehindtheScenes.html\" target=\"_blank\" rel=\"noopener noreferrer\">Library folder<\/a> of your project, which will cause Unity to rebuild it from scratch.\u00a0 Note that this can also take a long time with larger projects.\n<ol>\n<li>First you will need to locate your Library folder in the <strong>root<\/strong> of your <strong>project folder path<\/strong>. The easiest way to find it is by <strong>right-clicking<\/strong> your <strong>Assets folder<\/strong> in the <strong>Project view<\/strong> and selecting the menu item \u201c<strong>Show In Inspector<\/strong>\u201d in the context menu that opens. You should now see the <strong>Library folder<\/strong> there next to the Assets folder.<\/li>\n<li><strong>Close<\/strong> the <strong>Unity Editor<\/strong> if it\u2019s still open.<\/li>\n<li><strong>Delete<\/strong> the <strong>Library<\/strong> folder.<\/li>\n<li><strong>Relaunch<\/strong> the Unity Editor and open your project again. Unity should start reimporting all your assets immediately. If Unity crashes during this import process, try launching it a second time, as that oftentimes solves the issue.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Are you suddenly seeing errors in the Console originating from Power Inspector code, possibly triggered by making changes to code? In particular, are you seeing this error in your Log window: \u201cerror CS0246: The type or namespace name &#8216;x&#8217; could not be found. Are you missing an assembly reference?\u201d If so, it\u2019s possible that Unity\u2019s ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/docs.sisus.co\/power-inspector\/troubleshooting\/type-not-found-errors\/\" title=\"read more\">Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/posts\/321"}],"collection":[{"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/comments?post=321"}],"version-history":[{"count":2,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/posts\/321\/revisions"}],"predecessor-version":[{"id":556,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/posts\/321\/revisions\/556"}],"wp:attachment":[{"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/media?parent=321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/categories?post=321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.sisus.co\/power-inspector\/wp-json\/wp\/v2\/tags?post=321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}