Unable to build with WFS 1.2.7, --out error message

Even sample projects will not build. Here’s the error I get, any ideas?
wfs_error

It usually is a path error either for the keystore or your ouptut location. The keystore folder location is the .jks file not the parent /keystore folder.

The output location should be a legal folder sometimes it isn’t or has a non ascii standard character in it.

I think we’ve seen something like this with older Windows Computers too.

Open the log and scroll down to near the end to see if you can spot why it stopped?

Windows : C:\Users{User}\AppData\Roaming\watchfacestudio\dump\main.log
macOS : /Users/User Name/Library/Application Support/watchfacestudio/dump/main

Ron
Samsung Developer Relations

Hi Ron,

I checked all, the folder is writable. I also verified that an aab is generated by WFS in the destination folder, so it has write access. This is the error from the dump log, it seems to be looking for an apk but there’s no error indicating why there wouldn’t be one:

[1.2.7][9/17/202210:08:13 AM][undefined(buildListener.js:105)]
[1.2.7][9/17/202210:08:53 AM][EventEmitter.(captureListener.js:67)] [childWin][OffScreen14][did-create-window] id: 17
[1.2.7][9/17/202210:08:53 AM][EventEmitter.(captureListener.js:69)] [childWin][OffScreen14][did-frame-finish-load] frameProcessId: 4, frameRoutingId: 49
[1.2.7][9/17/202210:08:54 AM][BrowserWindow.(captureListener.js:88)] [childWin][OffScreen14][close]
[1.2.7][9/17/202210:08:54 AM][BrowserWindow.(captureListener.js:88)] [childWin][OffScreen14][close]
[1.2.7][9/17/202210:08:54 AM][EventEmitter.(captureListener.js:82)] [childWin][OffScreen14][destroyed]
[1.2.7][9/17/202210:08:54 AM][BrowserWindow.(captureListener.js:109)] [childWin][OffScreen14][closed]
[1.2.7][9/17/202210:08:54 AM][BrowserWindow.(captureListener.js:110)] [childWin][OffScreen14] childWebContentMap: [RunPreview,2]
[1.2.7][9/17/202210:08:54 AM][IpcMainImpl.(buildListener.js:69)] build start
[1.2.7][9/17/202210:09:01 AM][Socket.(BuildApk.js:291)] Missing input APK

[1.2.7][9/17/202210:09:01 AM][Socket.(BuildApk.js:291)] ‘–ks-key-alias’ is not recognized as an internal or external command,
operable program or batch file.

[1.2.7][9/17/202210:09:01 AM][Socket.(BuildApk.js:291)] ‘–out’ is not recognized as an internal or external command,
operable program or batch file.

[1.2.7][9/17/202210:09:01 AM][undefined(buildListener.js:122)] ‘–out’ is not recognized as an internal or external command,
operable program or batch file.

[1.2.7][9/17/202210:09:02 AM][undefined(buildListener.js:105)]

Workaround for anyone stuck like this. I wasn’t able to get cleanly past this, but here’s a workaround:

  • Manually find the aab. It’s generated in the folder you specify when you try to click Build.
  • Manually sign the aab:

WatchFaceStudio\tools\window\jdk\bin\jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore [YOUR_UPLOAD KEY.jks] [YOUR_AAB] [UPLOAD_KEY_ALIAS]

This aab can now be uploaded to Play Store.

I sounds like it was trying to open the keystore.jks file check your build settings to see if that location is set to the .jks file or to the parent folder.

If that is OK, Check the password that you created for the keystore or keystore alias. Make sure they are English Ascii characters and don’t have a . / or better still just alpha numeric characters.

Glad you got it signed.

Ron
Samsung developer Relations