Package name problem

Discuss
1

I developed an application but when I put the latest package name and press the button, I encounter a runtime error such as com.xyz.abc.Screen1
When I remove the package name again the error goes away
I tried different package name but the problem persists.
Plugins I use:
itoo+melon notification

2 Likes
2

Which package name did you choose?
Try something else
See also

.Taifun

3

com.limit.mssstudio or com.mssstudio.limit

all of them are wrong

4

refresh the kodular creator and try ur custome package name in other new app,is it show error or not? also show ur runtime error pic

5

I refreshed and tried again and again. When I press the button, the Melon and Itoo plugins are activated. They work even if there is no package name. Could it be that they did not accept the package name because I did not create a package name at the beginning of the application?
Also, since it is a clock, it constantly spawns this error.

WhatsApp Görsel 2025-04-22 saat 10.25.11_3d532384
WhatsApp Görsel 2025-04-22 saat 10.25.11_3d532384720×1600 25.9 KB

6

I think so. ur the first victim to this error.so try rebuild.

7

This is definitely the problem, I will create a new project and create the package name at the beginning and build the project from scratch

8

would u like to share ur aia file

9

yes ,I provide it private for you
I tried a copy in a new project but it still didn’t work.

10

I rebuilt the project from the beginning, the problem persists
What could be the problem??

11

Try with com.masstudio

12

image
image393×162 4.95 KB

I changed it but it keeps giving error with old package name
error spawn every second

13

Do not use limit, just use com. masstudiio

14

yes

image
image740×185 6.43 KB

and the error persists
Even though I changed the package name, the error comes with the old package name.

15

Did you test with fresh project?

Did you test in different device?

Are you sure there is no red mark count in blocks section?

If not works can you send us the copy of your project?

16

I am sending the copy, when there is no package name, the system works, when there is a package name, the system gives an error. There is no error, it was tried on three different devices.

Also, the project was created from scratch and the blocks were recreated one by one and the error persists.
I suspect it may be because an add-on does not recognize the package name. The problem is with button 3 and the melon add-on, maybe there is a problem?

17

Have you reviewed ?

18

I cannot test my companion with extensions due to kodular bug

From the conversion it is found that melon notification.

Are you using latest version? Remove this extension, reload the page and test

19

This is the latest version of the plugin but uninstalling it is a critical problem for the project I don’t understand why it doesn’t work it is an up to date plugin
You need to take a printout for the test

20

It is not a package problem. instead

image
image713×163 4.38 KB

morever you are using more than 10 clock timers, and few are related to melon apart from these few named clocks also you are using. So, it will be hard to find by anyone. You only should disable one by one to find out the fault block

  1. Component Instances:
    Ensure that all component instances referenced in the code (e.g., MelonNotification1, Itoo1, Label1, etc.) are properly initialized and exist in the layout. If any component is missing or hasn’t been initialized before it is used, this can lead to exceptions.
  2. Default Values:
    There are several blocks where component properties are being set to empty values (e.g., text fields initialized with no content). If any properties are mandatory and are expected to have initial values, this could result in runtime issues.
  3. Procedure Calls:
    The procedures GİRİŞ, color, circularcolor, and circular are invoked during the initialization. If any of these procedures contain logic that relies on uninitialized components or variables, it could lead to runtime errors. For example:
  • If any of the procedural calls is trying to manipulate component properties directly, ensure you are not referencing properties of uninitialized components.
  • If they depend on other procedures that have not been completely set up or need certain conditions met before execution.
  1. Permissions:
    The block where MelonNotification asks for permission (i.e., AskPermission block) implies that this needs to be handled correctly with user permissions. If it is attempting to perform actions requiring permissions that haven’t been granted, it could result in runtime issues.
  2. Logic Blocks:
    Ensure that logic comparisons and variable settings or comparisons (e.g., comparing global variables) are valid and initialized before their evaluations. If any conditional logic evaluates based on uninitialized variables, it could lead to unexpected errors.
  3. Error Handling:
    It would be beneficial to introduce error handling mechanisms within critical regions of your code, especially where component methods or properties are being accessed.
  4. Check Overrides:
    If any blocks are disabled (marked as disabled="true"), it could prevent the code from running correctly or as expected.

Debug:

  • Verify the existence and initialization of all components.
  • Check all procedure definitions to ensure they don’t try to access components that may not yet be fully available.
  • Review user permissions required for running the app if utilizing capabilities that require user agreements.
  • Implement additional logging or alerts to trace the flow of execution and identify where the runtime error occurs.

ref melon notif extension page for more to know how to handle it and how to connect with itoo extension for background work

Among the 13 clock components only clock 1 , sifrila, limit clock are not triggered at initially where as all other 10 clocks are set timer true during initialization, may be due to that it may happen

2 Likes