Kodular Fenix 1.5.6 Bug Tracker

[Vishwas (Vishwas Adiga)]

I have tested the fix with a broken project on my local instance of Kodular. Because workspaces fail to load as soon as malformed blocks are encountered, corruptions won’t be saved in our servers. Effectively, we’re still storing the pre-1.5.5 version of the affected blocks workspaces.

[bodymindpower (Anke)]

Is it really asking too much to get a short answer/feedback from the Kodular team on my suggestion?

Kodular Fenix 1.5.5 Bug Tracker

Storage Permissions (READ / WRITE) and DefaultFileScope The DefaultFileScope (AI2, Kodular: DefaultFile) property in the Designer doesn’t convince me at all. I consider this to be dispensable / superfluous (not to say: confusing). (Unlike AI2, this does not declare any permissions in the Manifest if DefaultFile is set to Legacy.) Why shouldn’t the storage permissions be declared like this (on all Android versions): <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> …

Kodular Fenix 1.5.5 Bug Tracker

And, as I said before, the File component should always declare both storage permissions (READ/WRITE) in the Manifest. WRITE permission only up to Android 10 (API 29). However, WRITE should not (never) be requested on devices running Android 11+. Or even better: Storage permissions should always be declared this way in the Manifest on all Android versions!

[bodymindpower (Anke)]

@Vishwas

We will be releasing an update this weekend

How about if we could test it on the test (beta) server beforehand?

[bodymindpower (Anke)]

Sound Recoder - bug

This simple app doesn’t work with the APK on Android < 11, because WRITE permission is not declared in the Manifest.

So again, for the fourth time:
Declare READ on all android versions and WRITE up to Android 10.

[bodymindpower (Anke)]

Video Player - bug - Play from assets

The Video_Player doesn’t play videos from the assets with the APK.

Video from assets still not works with new 1.5.5

Confirmed. Doesn’t work with the APK. This is the next bug among the countless other bugs… I won’t even try anymore to list all bugs.

This bug is still present since July 2019.

Video Player not playing assets programmatically

This bug still doesn’t seem to have been fixed since 2019.

[bodymindpower (Anke)]

Many storage permission bugs / issues can be fixed if these permissions are correctly declared in the Manifest. Here’s an extension that does it:

Declare Storage Permissions in the Manifest

Here is an extension, that declares storage permissions (READ & WRITE) correctly in the Manifest: DeclareReadWrite.aix (4.7 KB) <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="29" /> Since many components don’t declare storage permissions anymore after der 1.5.5 update, use this extension. Even if your app doesn’t need these permissions, it’s harmless and has no disadv…

Whether the permissions are then automatically requested depends on the respective components and must be checked (with the APK).

So if you found a permission problem, use this extension and report back if the problem persists.

[bodymindpower (Anke)]

Image component - Bug - WRITE must be declared incorrectly even on Android 11+

Image Editor component asking WRITE_EXTERNAL_STORAGE permission

Hello, The Image editor component is asking for WRITE_EXTERNAL_STORAGE permission (thereby getting denied by Android 11+ devices) when I try to call a function. [blocks] [error 908] I tried testing the app in two devices of Android version 9 and 11 respectively.

AIA

<a class="attachment" href="/uploads/short-url/ee2Ia4hQgOkc5Qqgb9bOTSAmNZu.aia">example.aia</a> (83.6 KB)

APK

<a class="attachment" href="/uploads/short-url/o21IerKOnlI55CbMQvx9…

Image Editor component asking WRITE_EXTERNAL_STORAGE permission

Of course, this is the next bug … (relevant on Android 11+)

[Connectappcreator (Connect App)]

Hi, they removed the return block. "if Load " “if show” for banner . This feedback was important to make the advertisement box visible only if advertisement does not occur errors. If propafganda is not loaded, there is a void in the middle of the app

[Vishwas (Vishwas Adiga)]

Please use the Failed To Load block to hide the banner if there was a no fill. We have removed some methods and events previously available in AdMob components to deter click-to-earn apps.

[Connectappcreator (Connect App)]

Ok, I implemented this block, where it tries to load the ad once again in case there is an error. or Then for the second time make banner invisible.

[Vishwas (Vishwas Adiga)]

Yes, this should work well.

[Johan_Lopez]

is the error Error 201 After Update 1.5.5 (Camera did not return an Image) - #20 by Anu10 listed on the weekend fix?

[Vishwas (Vishwas Adiga)]

Not yet, we’re still working on it

[Princeboy (Prince 🤴)]

Kodular update date

[bodymindpower (Anke)]

Player component │bugs, issues - 1.5.5 Update │ Shared folders

[ansi_nadubail (Mohammad Anas)]

This post was flagged by the community and is temporarily hidden.

[gio06 (Gio)]

Button image stays on the screen even I make its visibilty false. I mean its space disappear but image stays in the background.

test1.aia (25.3 KB)

[Boban (Boban Stojmenovic)]

@gio06

Button image stays on the screen even I make its visibilty false. I mean its space disappear but image stays in the background

This bug has been on Kodular for years and I doubt it will ever get fixed…

Buttons with custom images, and manually set sizes (45/45) wont go invisible on an event handler as expected

Show Feedback true causes this if the button contains image. [20190210_113957] Through the blocks work just to set to true, false do not. [bild] However, in the blocks it reports that it is false [bild] Something for @KodularCreator to take a look at. /Boban

[bodymindpower (Anke)]

@Boban

This bug has been on Kodular for years and I doubt it will ever get fixed…

… as well as some others …