.aab file not created. Error: EPERM: operation not permitted

Watch Face Studio
1

Hello! I still have the same problem. Can’t compile .aab in versions higher than WatchFaceStudio_1.1.14. Found this error in the logs main.log:

[1.3.13][08.01.202312:37:54][undefined(ProjectFileMaker.js:55)] [Error: EPERM: operation not permitted, open ‘D:\SOFT\WatchFaceStudio\tools\wfs_samples\Cats.wfs’] {
errno: -4048,
code: ‘EPERM’,
syscall: ‘open’,
path: ‘D:\SOFT\WatchFaceStudio\tools\wfs_samples\Cats.wfs’
}
[1.3.13][08.01.202312:37:54][undefined(projectListener.js:54)] [Error: EPERM: operation not permitted, open ‘D:\SOFT\WatchFaceStudio\tools\wfs_samples\Cats.wfs’] {
errno: -4048,
code: ‘EPERM’,
syscall: ‘open’,
path: ‘D:\SOFT\WatchFaceStudio\tools\wfs_samples\Cats.wfs’
}
[1.3.13][08.01.202312:37:54][IpcMainImpl.(buildListener.js:69)] build start
[1.3.13][08.01.202312:38:00][Socket.(BuildApk.js:291)] Unexpected parameter(s) after input APK (–ks-key-alias)

[1.3.13][08.01.202312:38:00][undefined(buildListener.js:122)] Unexpected parameter(s) after input APK (–ks-key-alias)

When I build the dial in version 1.1.14, then there are no such errors. Gave full permission to studio files and uninstalled antivirus. Nothing helped. Can someone help me figure out what’s wrong?

2

Hello,
I’m thinking that restarting the computer clears the caches may resolve the issue.

Did you try to uninstall the WFS and install it in the default path which is C:\Users\USERNAME\AppData\Local\Programs\WatchFaceStudio? I’ve seen it before too.

If your issue remains you can create a support request.

3

Many times already reinstalled in different folders. And in the default folders and on other drives. The error is repeated. And each time I rebooted the computer. Opened all permissions and nothing. If I install version 1.1.14, then everything works there. And the error in the log does not appear when compiling. I didn’t find any solution on the internet. Thanks for the helpdesk tip. Sent them a request. And how did you overcome this problem? Just rebooting the computer?

4

EPERM is a cannot read/write to file error

Create a new Keystore.jks and alias and see if that works I think they fixed a bug where the WFS allowed a keystore key that wasn’t allowed by Google Play Store.

A valid password can contain 6 to 30 characters, begin with an alphabetic character, and use only alphanumeric characters and special characters like Underscore (_), Dollar ($), Pound (#). The password must contain at least one number.

Cloud drives are often obfuscated if D drive is a cloud device that may be the issue. It also may be an issue that Boshra said that WFS is looking for something in the C:/USERS/username/ folder where it was installed.

Ron

5

Hello,

I don’t face the issue but see someone who faces it. The issue was resolved after freshly installing the WFS in the default path and creating a new Keystore file to build the project.
Did you try Ron’s way?

6

Hello guys! Thank you all very much for your help. The official answer from Samsung support helped with the solution. It seems to me that the problem was in the password to the keytor. There should be no special characters. That is why the problem was not solved because I used the old password for the new keystore.

Now I’m solving a new problem - how to transfer keys from the old keystore to the new one. It seems that this can be done in the Google Play Console itself. You need to download one watch face with a new key and use its data to update the key in all other watchfaces.