{"id":270,"date":"2016-03-09T01:50:51","date_gmt":"2016-03-09T01:50:51","guid":{"rendered":"http:\/\/fluentreports.com\/blog\/?p=270"},"modified":"2016-03-09T14:27:02","modified_gmt":"2016-03-09T14:27:02","slug":"nativescript-android-plugins-and-windows-path-size-issues","status":"publish","type":"post","link":"http:\/\/fluentreports.com\/blog\/?p=270","title":{"rendered":"NativeScript: Android plugins and Windows path size issues"},"content":{"rendered":"

If your on Linux or OSX you can skip this post; it only applies to us pathetic people that prefer Windows (like me ). I do have Linux and OSX, so maybe I'm not that pathetic; but since I do prefer Windows, maybe I am.<\/p>\n

If you don't want to read the reason this occurs but all you want is the fix; then scroll down to the fix<\/a>!<\/p>\n

Well if you see this error: Command [Some Path]\\gradlew.bat failed with exit code 1<\/strong> then you more than likely ran into this error if you see a lot of messages above it with \"No Delegate Set\" and errors.<\/p>\n

Well to understand the issue you need to understand that this is a issue between Windows, Gradle and how NativeScript (A fix might show up by v1.8 of NativeScript) currently does Android plugins. Windows, if it supported larger path sizes; this wouldn't be an issue (which is why it works on Mac\/Linux). NativeScript if it handled plugins differently might not run into this issue either. But at the current place we are at; it does so here is the crux of the issue.<\/p>\n

1. Windows only supports 255 character path sizes (if they are not UNC or Unicode path's)<\/p>\n

2. NativeScript scans all your plugins; any that have a platforms\/android folder; it will use the include.gradle<\/em> file found in that folder.\u00a0 If there is NOT a include.gradle<\/em> file; it will create one for you using the plugin name as the information.<\/p>\n

3. Gradle combines all the productFlavors (which are inside the include.gradle<\/em> files) into one long string.<\/p>\n

Ok, lets look at a sample include.gradle<\/em> file (this is also what is also generated for you, if it doesn't exist)
\n

android {\n    productFlavors {\n        "nativescript-websockets" {\n            dimension "nativescript-websockets"\n        }\n    }\n}<\/pre>
\nSo lets pretend your code exists at: C:\\nativescript\\AwesomeProject\\<\/strong>, so there is (32) characters. Now add platforms\\android\\<\/strong> (18). Next add build\\intermediates\\res\\merged\\<\/strong> (31) as this is where Gradle does its resource merging. So lets say you are using the Telerik NativeScript UI plugin; and lets grab one of the image names \\debug\\drawable-xxhdpi\\someimage.png<\/strong> which is of course adds another 49 characters. So this means we are using 130 characters already; leaving us with 122 characters left to play with.<\/p>\n
So if you have a plugin installed like nativescript-websockets<\/strong> you get 23 characters used just for a single plugin. I bet you can see where this is going. Add on the cool nativescript-telerik-ui<\/strong> plugin and you have another 23 characters used. Add just a couple more plugins, and yes -- you are now well over 255 character limit!<\/p>\n
Guess what happens??? \u00a0\u00a0 Well if you are following the story so far; you get a nice error that gradle quit with error 1.<\/p>\n
<\/div>\n
The Fix:<\/h2>\n
Now for the good news; here is how you can continue developing!<\/p>\n
    \n
  1. Go to your app folder and do a tns platform remove android <\/strong>to safely recover, you need to kill your existing android platforms folder.<\/li>\n
  2. Go into you node_modules folder, and then you need to repeat this next set of steps for EACH of the plugins you have installed.\n