Kodular Fenix 1.5.6 Bug Tracker

[Vishwas (Vishwas Adiga)]

Hi all

Please use this topic to report any and all bugs you may have encountered while using Kodular Fenix 1.5.6. We will be releasing an update this weekend to iron out major issues with the update while fixes to other bugs will follow shortly. I will triage reported issues and update the list below as and when we have updates.

Thank you for your patience!

Awaiting triage

• CREATOR-19 Storage Permissions (READ / WRITE) and DefaultFileScope (Kodular Fenix 1.5.6 Bug Tracker - #8 by bodymindpower)
• CREATOR-18 Screen orientation flips from landscape to portrait (Screen Orientation Quick Flip)

---

Under investigation

• CREATOR-16 WRITE_EXTERNAL_STORAGE denied (Error 908: The permission WRITE_EXTERNAL_ STORAGE has been denied. Please enable it in the settings app)

---

Fixes under testing

---

Fixed, awaiting release

• CREATOR-17 Download component requests WRITE permission (Kodular Fenix 1.5.6 Bug Tracker - #12 by bodymindpower)

---

[Bidush24 (Coding Never Lies..!)]

When the Mediation or Bidding Coming in the next Update?

[dora_paz (Dora)]

AAPT errors

YAIL compiler - AAPT execution failed.--> its a very simple web view app

I think i found out at which point this happens and to avoid this until it is fixed follow the instructions below When creating a new project, only name your project and ignore other settings, [bild] [bild] after the project is created you may change the setting of your project by going to settings.. [bild] @Vishwas @Diego

Colors issue

Error changing background color of component after updating to Fenix 1.5.4

What I did was to open archive / aia with 7zip and changed SDK from 19 to 21 and deleted projectColors. Saved projects settings, updated archive and uploaded to creator [image]

[Ambika]

The permission write external storage has been denied. This problem is coming in my app after update it was working fine before.

[Lily]

@Vishwas

Ad Manager Banners show wrong ad sizes

Even it takes too long time to get approved it is more than three days now my app have been not approved I have even sent mail to @diego but he haven’t replied please can you take a look on my request and can you fix this waiting approval in the new update

[Lily]

@Vishwas

Please use this topic to report any and all bugs you may have encountered while using Kodular Fenix 1.5.5. We will be releasing an update this weekend to iron out major issues with the update while fixes to other bugs will follow shortly. I will triage reported issues and update the list below as and when we have updates.

Hello @Vishwas is there any way to solve this as we are waiting for new update release
Because Google Play have said that

We reviewed Watani Wetu | Simba Vs Yanga, with package name com.watani.sc, and found that your app uses software that contains security vulnerabilities for users. Apps with these vulnerabilities can expose user information or damage a user’s device, and may be considered to be in violation of our Malicious Behavior policy.

io.kodular.info_netmovie.WPro.Screen1.lambda463 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4
io.kodular.info_netmovie.WPro.Screen1.lambda462 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4
io.kodular.info_netmovie.WPro.Screen1.lambda521 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4
io.kodular.info_netmovie.WPro.Screen1.lambda520 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4
io.kodular.info_netmovie.WPro.Screen1.lambda523 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4
io.kodular.info_netmovie.WPro.Screen1.lambda522 AAAAAZCYxqI:APA91bEktgb5toH0QqHwpJzCktR3Vuqkaby_6hgNs4Wp4FqYAQkcOEG0HBszrzSpMJmh3IV38kcp_NKREmvXhS7w3qW0yCHAjUETEzeMvfkQ5Ok498W34mlk4QLJXY15eX0c2_YPO6L4

See the screenshot

[bodymindpower (Anke)]

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"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="28" />

or this (since AI2 & Kodular decided to declare requestLegacyExternalStorage=true in the Manifest, so it continues to work on Android 10):

<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="29" />

I have already asked this question on the AI2 forum many times and have not yet received an answer.

Explanation
Since storage permissions are requested since API 23 (Android 6) at runtime, it should not be a problem / disadvantage at all to always declare them in the Manifest.

Only on Android < 6, storage permissions (READ / WRITE) are requested and granted at install time to be able to install an app.

You can remove them from the Manifest if the app doesn’t need them and if you don’t want users to have to grant them. However, this was also the case before.

So I would like to hear a single argument against my proposal.

The huge advantage, however, would be that it would simplify a lot and prevent countless permission bugs and issues. I have pointed this out in countless topics and posts in the AI2 forum.

[Lily]

@Ambika

The permission write external storage has been denied. This problem is coming in my app after update it was working fine before.

Yap, though it works fine when I use my Android version 9 but with samsung galaxy a13 5g it shows this error even if you allow permission on the Settings

I think this is why Google Play Team have rejected my app by saying that I am using a software that contains security vulnerabilities for users… expose user information & damage a user’s device

@Lily

We reviewed Watani Wetu | Simba Vs Yanga, with package name com.watani.sc, and found that your app uses software that contains security vulnerabilities for users. Apps with these vulnerabilities can expose user information or damage a user’s device, and may be considered to be in violation of our Malicious Behavior policy.

Please kodular staff do something on this we are real in trouble

[RAMDO (Dark Prince)]

One Signal Push Notification "Notification Opened" Block Not Working!

[*] I checked out https://community.kodular.io/t/bugs-in-kodular-eagle/34544?u=pavi2410 before creating a new topic Describe your issue One Signal Push Notification “Notification Opened” Block Not Working! The mobile device gets a Push Notification (Alert), when clicked it opens the correct app but nothing happens, as if the block or an app hasn’t realised that it is opened by Push Notification Click. It does not provide an id, title or message. (on the other hand, if the app is active then “N…

RTL problem in version 1.5.4

Starting with version 1.5.4, a problem arose in the RTL feature - certain components respond to RTL and components such as Layouts (also the main layout of the screen), Labels and more … do not change the layout direction and remain in the LTR display I have attached here a picture of the display in LTR and RTL, you can see that the title and the Tab Layout component change their direction properly and the layout where a button is located, and the direction of the text component are attached to…

RTL problem in version 1.5.4

The problem started with update 1.5.4, and it also exists in version 1.5.5

[bodymindpower (Anke)]

The Download component incorrectly requests WRITE permission also on Android 11+.

Since a file is downloaded to the Shared folder /Download, no storage permissions are required on Android 11+.

Error 908: The permission WRITE_EXTERNAL_ STORAGE has been denied. Please enable it in the settings app

… and the next bug … WRITE permission must be (incorrectly) declared in the Manifest also on Android 11+. The only way to do this is manually declaring it in the Manifest! https://community.kodular.io/t/an-update-from-kodular-staff/180827/122 https://community.kodular.io/t/fenix-1-5-5-new-file-system-file-component/186249/36

[bodymindpower (Anke)]

Canvas permissions:

Fenix 1.5.5 - New File system → File component

You don’t seem to get it like most. It’s not just about the File component, but about the entire new file system. The Canvas component also does not declare any storage permissions (regardless of the DefaultFileScope), so the same problems occur here as well. First check the new file system and then come back with useful contributions.

[Anu10 (Anu)]

Screen Orientation Quick Flip

Screen Orientation Quick Flip

This bug was declared fixed in the new update(1.5.5), but it still persists. There is nothing in blocks, nor decompiling the apk, that is possible as a quick fix. I’ve already tried several ways (maybe I lack knowledge), but nothing has been able to prevent, even provisionally, this event.

Screen Orientation Quick Flip

Yeah if the device is hold in portrait position everything seems to be working fine. But if holding in landscape position & screen orientation is set to portrait, flipping behaviour of next screen is observed as you mentioned. Device Auto Rotation Property was also locked. Tested on Redmi Note 7 (Android 10)

---

• Tested on Redmi Note 7 (Android Version 10)

• Auto-Rotation property was also locked.

• Screen Orientation was set to Portrait in designer section.

• Flipping only occurs when holding in landscape position, it works properly when holding in portait position. (This behaviour not observed in apps created with Android Studio)

---

Reference Video

[Vishwas (Vishwas Adiga)]

@Vishwas

• Projects with File component are broken (All my projects which use File Component are broken due to this new update )
• File component properties do not load (Kodular Fenix 1.5.5 Bug Tracker - #10 by ToitoineGaming)

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

[bodymindpower (Anke)]

@Vishwas

Projects affected by this bug will automatically be recovered/fixed when the update is released.

Good to hear that. Can we definitely count on that?

[bodymindpower (Anke)]

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!

[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.6 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.6 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?