Since NS7 update, some plugins fail building with "Error: spawn ./gradlew EACCES"

Offen

#5,368 erstellt am 04.9.2020 7 Kommentare 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@rigor789 arbeitet bereits daran.

Seit 04.9.2020.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

I personally haven't tested it on Windows, so there might not be any problems on that platform because the build scripts are handled separately.

Since the update to NS7 a few days ago, there have been multiple people on the NSCommunity Slack reporting this. I personally have encountered the problem in relation to nativescript-socket.io, but it's not specific to it, as it actually boils down to an issue in the CLI.

The problem is two-fold: first, the EACCES error is caused by the gradlew file not being being marked as executable. Once this is fixed, errors relating to the carriage return character start popping up. The issue now is that the gradlew file uses windows style newline (\r\n) instead of *nix style newline (\n). I've implemented a quick and dirty fix, but this only solves the symptoms, it doesn't solve the problem at the root cause as I'm not familiar enough with NS to know which part of the tooling generates the gradlew file when building plugins.

The temporary fix involves editing a file in the NS CLI:

in the global node_modules folder (unless NS is locally installed under the project's devDependencies), find nativescript/lib/services/android-plugin-build-service.js
anywhere at the top of the file (maybe between lines 19-24 for consistency's sake) add const fs = require("fs");
at line 413 (formerly 412 before the above addition) add:

if (!this.$hostInfo.isWindows) {
    const gradleFile = path.join(pluginBuildSettings.pluginDir, gradlew);
    let content = fs.readFileSync(gradleFile, {encoding:'utf8', flag:'r'});
    content = content.replace(/\r/g, '');
    fs.writeFileSync(gradleFile, content);
    fs.chmodSync(gradleFile, 0o755, (err) => {
        if (err) {
            console.log("Error changing setting gradlew as executable");
            throw err;
        }
    });
}

Vorherrschende Sprache: JavaScript
Sterne: 1.1k
Forks: 204
Ø Merge: 1 T. 9 Std.
Gemergte PRs (30 T.): 8

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NativeScript/nativescript-cli

cli does not recognize physical iOS devices (since cli 9.1.0) Offen

in-progress

NativeScript/nativescript-cli#6140 · 2 Kommentare · 1 zugewiesene Person · Erstellt am 31.8.2026
Fix cleanup request removal presence check logging Offen

NativeScript/nativescript-cli#6090 · 1 zugewiesene Person · Erstellt am 25.7.2026
ns 9 running test after running the app starts the app not the test runner. Offen

in progress

NativeScript/nativescript-cli#6015 · 1 Reaktion · 1 zugewiesene Person · Erstellt am 01.5.2026
[note]: SPM preferred over Cocoapods going forward with plugins Offen

question

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100

NativeScript/nativescript-cli#5992 · 5 Kommentare · Erstellt am 26.3.2026
feat: default output could suppress xcode build logs, enable via flag Offen

feature-pending-triage

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100

NativeScript/nativescript-cli#5975 · Erstellt am 27.2.2026

Alle Issues in NativeScript/nativescript-cli