Besides that, it´s generally a good idea to stick to a release tag rather than to follow the latest commit: latest commit is per se a work in progress and not necessarily yet aligned with all submodules.
Try the lv_micropython v1.20 (was merged few days ago, lv_micropython is now aligned to micropython 1.20) together with the latest LVGL release v8.3.7
Also: screenshots of errors are a bad idea. They are not parseable,one cannot copy text, and search engines do not index their content !
I’m trying to keep lv_micropython master branch stable enough. For that purpose, every PR or commit passes multiple tests building it on different ports and running all LVGL Python examples automatically.
While it’s still possible there would be issues with latest commit of master branch, it’s fairly rare and I believe many people are relying on master branch.
If you are looking for the most stable and tested version, you can use release/v8 branch on lv_micropython. But then you won’t have latest Micropython. LVGL v8 is also a bit behind.
I can confirm, that latest lv_micropython master commit is stable (ports: unix, esp32), I also deployed port ESP32 - boards: M5Core2 and LilyGo TWatch2020 (board definition not yet pushed to git), and both work on real devices.
(there are only 2 LVGL related bugs, but those does not affect lv_micropython 1.20.0 build)