Screen AlignHorizontal arguments error

[Xdev]

Error from Companion: The operation AlignHorizontal cannot accept the arguments: , [“3”]
Error from Companion: The operation AlignHorizontal cannot accept the arguments: , [“2”]
Error from Companion: The operation AlignVertical cannot accept the arguments: , [“3”]
Error from Companion: The operation AlignVertical cannot accept the arguments: , [“2”]

[AryanGupta]

Currently, there is a bug in companion. it will be fixed soon.

[Xdev]

You can tell me the time till when it will be done.

[MohamedTamer]

Please try to update your companion and let me know if it works.

Appzard Companion

Hello everyone, We are happy to announce that the companion for appzard has been launched! With the companion, you can test your app in real-time, without having to build and download it every time you want to apply your latest changes. Screenshots [tia1686048148] [tia1000590166] [tia1472173507] [tia368064348] [tia764838726] [tia2121445233] Download Direct Download: Appzard Companion.apk Google Play: Comming Soon… Cheers, Mohamed Tamer

[Xdev]

This is not a companion problem

[Xdev]

any update sir please solve problam

[Xdev]

Please solve this problem immediately arrangement not work in apk

[AryanGupta]

Please create a new project. There are some issues in old AIA.

[Xdev]

I have created a new project. Still this problem is happening.
It has to be resolved as soon as possible.

Uploading: photo_2022-09-10_11-05-32.jpg…

[MohamedTamer]

This bug should be solved by the latest update:

Appzard 2.0

This is a bug fix for the most major bugs reported on the community. Bug Fixes Fixed app crashes when using the FirebaseDB component Fixed a bug in the file component Exists method for assets in APK Previously, the Exists blocks would always returns false when the scope is set to Asset in APKs Fixed most designer properties crashing the app when changing their default values Properties such as AlignVertical, AlignHorizontal, and ScreenOrientation would now work properly! Fix crash …

[anduramon]

hi, thanks for the hard work. I present this error.

[AryanGupta]

This bug is fixed already. We will update you when it’s live. However, this bug doesn’t occurs in APK.

[anduramon]

Thanks so much.

[BodyMindPower]

@AryanGupta

However, this bug doesn’t occurs in APK.

Unfortunately it does, it also occurs with the APK.

[MohamedTamer]

Can you please try again with the new component?

Appzard 2.0

Bug Fixes Fix Image Picker component crashing when clicked Fix List Picker component crashing when opened Fix ImageListView component not picking the correct path for images in the companion You should now prefix assets names with // (ex.: "//image1.png") and it would work correctly on both companion and APK Companion The companion now targets API 33 (Android 13). It was incorrectly targeting API 30 before. Fixed errors when using some properties in the companion Fixed Incorrectly decla…

[Quantum20]

This error continues and will continue giving (Why?)
If you look closely it seems that in appzard the visual property has a name and the internal one has another one!

The solution to it is to use this component

And it occurs in two moments, when you create dynamic components, declaring its name with text and creating its properties and when you use the physical component and insert Integer Numbers in it.