Error From Creator {apply-to-args}

Feedback Bugs
, , ,
1

Runtime Error in Latest Kodular Update (apply-to-args issue)

After updating to the latest version of Kodular, my project started throwing a runtime error that did not exist in the previous version.

The crash happens when running the project in Kodular Companion. The error trace suggests it is related to procedures/events handling (probably when a procedure or event is triggered with arguments).

This is a regression bug because the exact same project ran fine in the previous Kodular release without any issue.

:warning: Error Trace

Argument () to 'apply-to-args' has wrong type (gnu.mapping.Values) (expected: procedure)
at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:170)
at gnu.mapping.ProcedureN.apply1(ProcedureN.java:31)
at io.makeroid.companion.Screen1.processException(Screen1.yail:10101)
at io.makeroid.companion.Screen1.dispatchEvent(Screen1.yail:10157)
at com.google.appinventor.components.runtime.EventDispatcher.hxYOFxFjLpN1maJuWNxUV40nExCGxsxkDPOTgtzMu4zlZCQb3bPlKsXo1SYJg6ME(SourceFile:242)
at com.google.appinventor.components.runtime.EventDispatcher.dispatchEvent(SourceFile:198)
at com.google.appinventor.components.runtime.Form$15.run(SourceFile:1094)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:224)
at android.os.Looper.loop(Looper.java:318)
at android.app.ActivityThread.main(ActivityThread.java:8720)
at java.lang.reflect.Method.invoke(Native Method)
at com.google.app.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:561)
at com.google.app.internal.os.ZygoteInit.main(ZygoteInit.java:1013)

:white_check_mark: Expected Behavior

This image shows a block-based code snippet initializing a global list variable named 'name' as an empty list and setting the text of Label1 to the second item in the 'name' list when Screen1 initializes. (Captioned by AI)
This image shows a block-based code snippet initializing a global list variable named 'name' as an empty list and setting the text of Label1 to the second item in the 'name' list when Screen1 initializes. (Captioned by AI)536×211 9.24 KB

The project should run without errors (as it used to in the previous version of Kodular).

:cross_mark: Actual Behavior

The project crashes with the error above when certain procedures/events are triggered.

Observations

  • The bug appears only in the new release of Kodular.
  • In the last version, this issue never appeared with the same project.
  • The error seems connected to procedure calls or event handling, possibly due to internal changes in the ApplyToArgs / EventDispatcher implementation.
  • Could be a regression from recent updates that broke compatibility with projects created earlier.

Please investigate if the recent Kodular update introduced a regression in the event/procedure system now its 5 days, i was think that my project got issue, but even new ones do the same.
This error makes it impossible to run my project in Companion

@Diego @Taifun

1 Like
2

You are trying to access an element of index 2 in an empty list. Can you make sure that the element exists before trying to access it?

1 Like
3

I did this to see if it throw anything related to an empty list, but its not give expected error. Or do you also update the apply-to-args into this way?
Its must throw something like this telling where i did wrong

Ekran görĂŒntĂŒsĂŒ 2021-07-21 173648
Ekran görĂŒntĂŒsĂŒ 2021-07-21 173648572×192 13.3 KB

After getting this error companion don’t respond again unless i reconnect, which i have ever experienced, and it happens in all my projects

See also here

A screenshot of a coding interface with a long block of text code at the top and a visual programming block area at the bottom, displayed within a web browser window on a desktop. (Captioned by AI)
A screenshot of a coding interface with a long block of text code at the top and a visual programming block area at the bottom, displayed within a web browser window on a desktop. (Captioned by AI)1600×811 229 KB

Here its RecyclerList instead of view.findViewWithTag(tag) must not be null its repeat the same issue

1 Like
4

Hey am sorry @Diego to tag you again, but I have been waiting for response from you since yesterday never heard anything about this issue, it’s only from my side?

Because I can’t run any project now if any argu appear companion stuck

2 Likes
5

I’m looking into this now. Can you check if it’s also happening in exported APK files in the meantime?

EDIT: I’m not able to replicate it. Do you have an AIA file to test with?

6

In exported APK it throwing normally error, eg findviewbytag must not be null, this happens only in the main creator, when running the project in companion, it’s not mentioning what’s the problem.

7

I was able to replicate the issue, and the actual problem is that you are trying to access a list item which does not exist. The error is misleading, but that seems to be the issue.

8

I’ll step in for a moment because I think there’s some misunderstanding.
Ibrahim is performing this operation specifically to demonstrate Kodular’s abnormal behavior.

Normally, executing this operation would trigger the usual error indicating that we’re selecting the wrong index.

Instead, this time it produces an error that crashes the app or the companion.

2 Likes
9

As I said here, I wasn’t using this method, but I was try to catch it and show it here, instead of normal errors response it throwing apply to argue

Sample.aia (235.3 KB)

1 Like
10

I agreed with @Ibrahim_Jamar said, I’m also facing an issue on a runtime error; when there is an error happen the dialog will show what the exact error for small instant and replaced with wrong type {apply to args}
 instead of showing exact error.

An error message window displaying a runtime error related to a wrong argument type in a software application, with detailed technical information and a 'Dismiss' button at the bottom left. (Captioned by AI)
An error message window displaying a runtime error related to a wrong argument type in a software application, with detailed technical information and a 'Dismiss' button at the bottom left. (Captioned by AI)1199×280 42.2 KB

1 Like
11

I have added it to the bugs tracker, but unfortunately has lower priority than other bugs, as it’s just about exception reporting (and not an error as such):

12

I am unable to understand why this error is showing on Kodular Companion app. Can somebody help me to understand this issue?

IMG_20251015_222952_698
IMG_20251015_222952_6981920×1440 190 KB

13

Hi vijay,

Welcome to the :kodular:odular community!

It’s a known bug,

meaning there’s an error in the blocks.
If you show them to us, we can help you fix the problem.

14

Hi,
Try to remove blocks from the screen1 intiallize
Then try to Intialize Also can you show which extensions and blocks you’re using?

15

All my old projects before Kodular update was working fine but now giving " [warning Runtime Error: Argument () to ‘apply-to-args’ has wrong type (gnu.mapping.Values)]" error and even after exporting apk and after opening it gets stuck on white screen and app automatically closes.

16

This issue comes in with Kodular creator version 2025.8, after facing it in my all project I reported it on 18 August, I was hoping that the next update they will deal with it but still throwing the same error,

I suggested you to remove any blocks from when screen1intiallize block and try again

17

I tried removing blocks but nothing worked. even i removed all extensions but still same issue.

18

Do you have clock component that is enabled by default?

19

apply-to-args is, in any case, a very simple error, just like in the example Ibrahim showed in his report.
There’s definitely some block that’s set up incorrectly.
In your previous projects, the error might have been ignored because it wasn’t blocking.
I’d ask you to show your blocks, if possible.

20

Did you removed OneSignal component?