I can't open a file in /data

[mimimix]

I just need to read the file test.txt , but when I try to get a file or the contents of a folder, I always get undefined. What I'm doing wrong :(

[silver-zepp]

Refer to the hierarchy on this doc: https://docs-testing.zepp.com/docs/guides/framework/device/fs/

It looks to me that your data folder is stored outside the assets folder. In the future please make sure you attach a reproducible project. It can get very tricky to debug a screenshot. @mimimix

[mimimix]

fileTest.zip

[silver-zepp]

I see now. Here's a working example for you to play with:

import { openAssetsSync, readSync, } from "@zos/fs";

const FILE_PATH = "data/test.txt";

function bufferToString(buffer){
  return String.fromCharCode.apply(null, new Uint8Array(buffer));
}

Page({
  build() {
    const fd = openAssetsSync({
      path: FILE_PATH,
      flag: O_RDONLY,
    });

    const buffer = new ArrayBuffer(1024);
    const result = readSync({
      fd,
      buffer,
    });

    if (result > 0) {
      console.log("readSync succeed");
      console.log(bufferToString(buffer));
    } else {
      console.log("readSync failed", result);
    }
  },
});

Your hierarchy for this project should be: assets/390x450-gts-4/data/test.txt
fileTest-fixed.zip

[silver-zepp]

[mimimix]

After updating zeus-cli to 1.3.0-beta.12 everything worked.
But sometimes an error occurs at startup (also relevant for the previous version of zeus):

info  connecting to simulator
success  simulator connected
rebuilding...
info  Start building package, targets: 390x450-gts-4.
node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:405:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1118:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Node.js v20.6.0

But it starts 2-3 times

[silver-zepp]

I'd say it has something to do with node rather than zeus, never seen this issue, and considering you've met it with both versions it's most likely a node.js issue. Maybe a corruption. But it also might be that it's not supported. I haven't heard anyone having this before and people tend to use the most recent versions. Weird.

I personally still use v16.14.0. Try installing the LTS version?

[mimimix]

When I installed node 18.17.1, the error disappeared :)
Thanks for the help

[silver-zepp]

Awesome! Glad we got it all sorted. Happy hacking @mimimix 👋

[SashaCX75]

I also had problems with reading files.
I saved the file using hmFS.write and then read it again using hmFS.read. Everything works until I restart the programme in the simulator. That is, when I make changes to the programme and run it again in the simulator, the previously saved file disappears. On the watch everything works correctly and the file does not disappear.

[silver-zepp]

That's a flaw in VM's design. When you work with the filesystem on the Simulator and you want to interact with files, you need to make sure that you don't push any updates on the VM. In other words, do not restart the VM by re-saving the project in the VSCode. This way destroys the /data folder and all its contents.

You will have to exit the app with a Left -> Right swipe or press the Home button, and then enter into it again to have your FS changes persistent @SashaCX75

[SashaCX75]

@silver-zepp This only partially solves the problem. While I'm working with one version of the program, this method works. But as soon as I update the program, the saved data will still disappear.

It would not be bad to add such a feature to the description of the operation of these functions when working on a simulator. I spent a lot of time thinking that I was not storing data correctly and trying to solve this problem.

[silver-zepp]

I hear you @SashaCX75. I reported this 4 months ago as well, but it never got into the right hands or was lost in translation. My suggestion was to add an option in settings to clear the storage only when required. I'll make sure that this time it will be heard.

[silver-zepp]

This was fixed for multiple devices. Look for the VM update with the remark "Improve Mini Program installation speed". If it has it then the storage should be properly working @SashaCX75

[SashaCX75]

@silver-zepp Thank you. In versions of the simulator where there is such a note it is corrected. But it seems to be only for models on ZeppOS 2 and newer. And I was just working with GTS 3 and it's not fixed there yet. I hope it is temporary.

I would also like the screen outline to be greyed out like in Balance simulator. It is very convenient, you can see the screen borders at once.

[oakeley]

@silver-zepp I am trying to communicate with the phone via an http connection to 127.0.0.1. The watchface uses a miniapp only as a bridge. The miniapp writes the http results to a file that the watchface then loads. Can you recommend an alternative method for getting data from the phone to the watchface?
In Zepp v1 and Zepp v2 the following command in the watchface works:
const file = hmFS.open(filename, hmFS.O_RDONLY);
I have tried this but it still doesn't work:
const file = hmFS.open(filename, hmFS.O_RDONLY, {appid: 28962});

Many thanks for your help

[oakeley]

Is there a page somewhere that lists all of the @zos/fs features? Specifically it would be super helpful for developers if you could expose an "autocomplete" for vscode that includes the @zos capabilities... Thanks