Hi,
Just tried to publish my app, and the components normally published to uibuilder/components/reusable are not there any more !
Please help asap as I cannot build my app which I need to deploy tomorrow morning.
Thanks
Hi,
Just tried to publish my app, and the components normally published to uibuilder/components/reusable are not there any more !
Please help asap as I cannot build my app which I need to deploy tomorrow morning.
Thanks
Hi @Nicolas_REMY,
Yesterday we had issues on our side and that could call this unexpected behaviour. Unfortunately I wasn’t able to reproduce this issue on my app right now. All reusable components are present in the published app.
components normally published to uibuilder/components/reusable are not there any more.
Are these components missing in the published app and present in the preview mode?
Regards,
Olha
Hi @olhadanylova ,
Yes, the app works fine in preview mode, but when I publish it, the components folder is almost empty !
Only the custom
folder is built, but nothing else. My change control drew my attention to the fact that about 90 subfolders which should be in reusable
were missing compared to the previous version (!)
I also noticed that the publication process is different from usual :
If I remember correctly, the modal disappeared when the “Please wait for a while, the app is being published” overlay appeared. Here, both happen stayed onscreen.
You can try publishing my app. Its ID is D7075715-5086-625A-FFAB-39C2F40FB200.
Thank you for the details. We’ll investigate this issue as soon as possible.
Any news, please ?
Our UI developers found an error while publishing, and working on it.
We’ll let you know as soon as there’re any updates.
We were able to reproduce the issue and already working on the fix, the ticket’s number for reference is BKNDLSS-30410
Sorry for the inconvenience, we know how it is important for you and fix it asap!
Is there a workaround that I can use in the meantime ?
The fix has been released.
Could you please check?
Thanks, but sorry, I missed my deadline. Not available before tomorrow morning now
I hope it works because I will really need it to work tomorrow.
Thanks for the effort !
Sorry for this inconvenience.
We’re trying our best to fix issues as soon as possible and prevent the new ones, but sometimes something doesn’t go according to the plan.
Hi, sorry to report, but the issue is NOT fixed
I even tried to publish into another, new folder, but the same goes. The symptoms are the same : the modal does not disappear when the overlay appears in the background, and the reusable
components are not generated.
I really counted on it working this morning.
Can you please look into it ASAP and provide a workaround in the meantime ?
Thanks.
Hello, @Nicolas_REMY.
We are working to resolve the issue, sorry for the inconvenience.
Best Regards, Nikita.
Any news ???
Really, I need a workaround.
We are working on it. When the problem is fixed, we will notify you immediately.
the fix has been released several minutes ago, could you please try to publish it from your side?
Only the
custom
folder is built, but nothing else. My change control drew my attention to the fact that about 90 subfolders which should be inreusable
were missing compared to the previous version (!)
in the published (built) app there is no resuable
folder anymore because all files are compressed in order to improve loading performance for production apps
Hi @vladimir-upirov , thank you for the update.
Good to have the info about the reusable
folder not existing anymore. Where are the files compressed now ?
And @Nikita_Fedorishchev, does this change the native mobile app shell process ? Can you confirm that I don’t need to add all the assets/ui_builder/components/reusable
folder and subfolders to pubspec.yaml
anymore ?
they go into the following files
This needs to be tested. But I guess adding annotations to pubspec.yaml
is no longer required.
OK, indeed I managed to build without having to list all reusable folder. That is quite nice.
It has just been a pain not being able to publish and build just when my release was due, but thanks for the effort in fixing the issue.