All my projects which use File Component are broken due to this new update

[Lily]

@Boban

Are you really sure that the file component is the cause to it

yap from my end I edited the Screen1.scm and Screen1.bky by removing the File Component the my project worked fine as previous

[Lily]

@AC_Automacao_e_Controle

Screen1.bky file.

Can you try to remove them and import an aia to see the result!

[AC_Automacao_e_Controle (AC Automação e Controle)]

Lily, if you have meant do delete all references on FILE1 in .scm and .bky files, yes, it ceases all error. Only 1 warning remains.

In Screen1.scm: {"$Name":“File1”,"$Type":“File”,"$Version":“7”,“Uuid”:"-177562226"},

In Screen1.bky, several occurrences: I had to delete all <block> tags that contained FILE1. Only removing tags <mutation> and <field>, where FILE1 indeed was present was not enough.

At this moment, if I decide to not wait for solution from Kodular staff, I will have to spend a lot of time to rebuild everything related to file read and write.

Kodular team should make available previous Kodular version to those who has developed many and/or big projects in order to prevent such a waste of time, till they solve this problem related to FILE component.

That’s pretty serious. My app is (was?) next to its commercial release and all of a sudden everything gets messed up.

[AC_Automacao_e_Controle (AC Automação e Controle)]

One more info: I’ve just created a project to test FILE component inclusion: an error happens immediately.

No matter if an early Android version (5.0) or not (10).

Adding other storage components, no error is thrown.

So, there’s something really bad with FILE component.

[bodymindpower (Anke)]

@AC_Automacao_e_Controle

I’ve just created a project to test FILE component inclusion: an error happens immediately.

Fenix 1.5.5 - New File system → File component

In addition the File component does NOT declare any storage permissions (with DefaultFileScope = App) in the Manifest. Unfortunately, my fears came true that the AI2 bugs were not fixed. It seems to be even worse.

[Lily]

@AC_Automacao_e_Controle

Kodular team should make available previous Kodular version to those who has developed many and/or big projects in order to prevent such a waste of time, till they solve this problem related to FILE component.

I hope @Diego will advise his staffs to do so

@AC_Automacao_e_Controle

That’s pretty serious. My app is (was?) next to its commercial release and all of a sudden everything gets messed up.

This is so sad

@Fenix 1.5.5 - New File system → File component

In addition the File component does NOT declare any storage permissions (with DefaultFileScope = App) in the Manifest. Unfortunately, my fears came true that the AI2 bugs were not fixed. It seems to be even worse.

I knew why they said that it is a fix but for the real they meant to deprecate only AdMob so that we can’t earn any penny and at the same time the Google Ad-manager is not something quick to depend on since the approval takes time and sometime it is not approved anymore

If @Diego can think twice of this he will actually restore the previous version else we are wasting time on this Kodular Platform

[AC_Automacao_e_Controle (AC Automação e Controle)]

If I’m not wrong, these non-code Android app development platforms (Kodular, App inventor, Thunkable…) generate projects that are not interchangeable. Indeed, till now I have not spent any time checking up if there’s some ‘low level’ (or not so ‘high level’) to make a project file accept by another platform.

By now, an issue related to an important component as the FILE one is impacting a lot.

Hope someone from Kodular staff deal with this as soon as possible.

[Z3pp3l1n_CeVe (Zeppe)]

I did it too to resolve the problems

[Boban (Boban Stojmenovic)]

Since you have the same block in your project

I bet is the same issue as here

Error in 1.5.5: “The blocks area did not load properly. Changes to the blocks for screen Screen1 will not be saved"

To overcome the error until it’s get fixed Open the broken screen .bky file by using 7zip and edit. [bild] Find method_name=“Exists”, select and cut but only if it contains type text block [bild] paste just below </block> [bild] do this process if you have multiple Exists block P.S there might be other blocks as well that causes this error As you can see we are unable to attach type text to scope but in the above example it is and there by it breaks the whole project [Fileexists]

[AC_Automacao_e_Controle (AC Automação e Controle)]

Here to shift forward the date to close this topic.

No manifestation from Kodular team till now. Until a new version correcting this issue, they could avail the previous operating one, so we could be spared from this situation.

I had to remove FILE component and related blocks and change a lot of other things to make my app back to work in degradated way. It’s important to my app that a simple local storage is working.

[Vishwas (Vishwas Adiga)]

Hi
Apologies for the inconvenience, it seems to be an issue with a particular method in the File component as a result of which projects aren’t being brought over to the latest version of Kodular without getting corrupted. We’re currently looking into the issue and will have updates soon. I would recommend taking backups and holding tight till the fix is released.
Regarding other issues in the File component, we will need some more time to triage and fix them.

Thank you for your patience and once again, apologies for any disruptions in your workflows.

[bodymindpower (Anke)]

Thank you for finally giving us feedback.

[bodymindpower (Anke)]

@Vishwas

I would recommend taking backups and holding tight till the fix is released.

This should be visible in a prominent place and not just within a single thread.

Fenix 1.5.5 - New File system → File component

I’m afraid that all projects containing the File component opened after the new update (Fenix 1.5.5) will be corrupted beyond repair. So I strongly recommend making a backup of the project beforehand!

[Vishwas (Vishwas Adiga)]

Kodular Fenix 1.5.5 Bug Tracker

Projects affected by this bug will automatically be recovered/fixed when the update is released. Thank you for your patience

[AC_Automacao_e_Controle (AC Automação e Controle)]

Vishwas, would it be possible to avail previous stable version in order to allow FILE component users to use their working projects?

[Vishwas (Vishwas Adiga)]

A bug fix update is going to be released this weekend which will resolve issues with broken projects due to the File component.

[bodymindpower (Anke)]

@AC_Automacao_e_Controle

would it be possible to avail previous stable version in order to allow FILE component users to use their working projects?

The File component can be replace with one of the File extensions from @Taifun or @vknow360 and or my MFile extension.

[AC_Automacao_e_Controle (AC Automação e Controle)]

Thanks, Vishwas!

[AC_Automacao_e_Controle (AC Automação e Controle)]

Hi!

It’s a pity only now I’ve got this information.

I’ll wait for Kodular solution till this weekend, as Vishwas has stated. If some delay comes to happen, I’ll try the File extensions you’ve suggested.

Thanks a lot!