You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
When building my project for Release I noticed a build error: /gradlew.bat failed with exit code 1.i think that because my project path contains Space. if there is not space in the path release build is working properly.
Try to find any similar issues at stackoverflow.com or other websites can't find any.
Version numbers:
tns: 2.5.2
Cross-platform modules: 2.5.0
Package.json of project:
I managed to reproduce the same crash when building in release. I found that passing a relative/absolute path (both resolve to full paths) with whitespace(s) in it to the --key-store-path argument will cause the errors.
The current workaround is to use a keystore file from a path that doesn't contain whitespaces.
@Khadreal we'd need the complete log to be able to determine the reason for the build exception. Please run tns run android --log DEBUG and share the logs.
@AmilaRukshan commented on Thu Mar 16 2017
Hi,
When building my project for Release I noticed a build error: /gradlew.bat failed with exit code 1.i think that because my project path contains Space. if there is not space in the path release build is working properly.
Try to find any similar issues at stackoverflow.com or other websites can't find any.
Version numbers:
tns: 2.5.2
Cross-platform modules: 2.5.0
Package.json of project:
--log trace output:
@Pip3r4o commented on Fri Mar 17 2017
Hey @AmilaRukshan
I managed to reproduce the same crash when building in release. I found that passing a relative/absolute path (both resolve to full paths) with whitespace(s) in it to the
--key-store-path
argument will cause the errors.The current workaround is to use a keystore file from a path that doesn't contain whitespaces.
@AmilaRukshan commented on Sat Mar 18 2017
Thanks a lot @Pip3r4o .i tried your workaround its works for me.
@Pip3r4o commented on Fri Mar 24 2017
A fix will be available in the upcoming 3.0 NativeScript version.
#2648
Thanks for using NativeScript!
The text was updated successfully, but these errors were encountered: