Hi, I’d like to know how you’re doing with this. I’ve been stuck for a couple of days. My app was working fine, but it’s been experiencing this issue for a week now.
Hi, I checked the app today and the same problem persists. Does anyone know how they’re handling this problem?
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?
this was my problem today, and i fixed it, thank you very much…i was getting information into my list view from google sheet while the column cell was empty ![]()
I’ll just add to this to say that this bug is quite serious and an absolute pain for larger projects published on the Play Store.
…which is painful when the Play Console gives a crash stacktrace and all it says is this:
(Yes it is my fault and I’m tearing my hair out trying to locate the cause since I’m unable to repro the crash…)
I think I have some good news… This bug has been a complete headache, but I think it’s finally fixed:
This is the used AIA, which should be crashing in the “normal” Companion:
GloriousCyanPanther.aia (2.4 KB)
I’ll test a couple more things, but if I don’t find anything else, I’ll publish it to Play Store.
I’ve just submitted an update to Play Store for the Companion which should have fixed this issue.
Thanks a lot @Diego
appreciate
I don’t see it on the 2025.10.4 release notes. Since the error applies not just to the Companion but compiled apps too, surely there is some change in the Kodular Creator itself, that allowed you to fix the issue?
The error was only in the Companion, or that is what was mentioned. If it’s also in compiled apps, then that will be published in the next one along with other fixes.
Look at my post from 28 days ago right before you posted here 10h ago. :')
Agh missed that Play Console crash report, sorry… ![]()
At least for now it should help debugging. I’ll release 2025.10.5 having the full fix for compiled apps, along with other fixes, this weekend.
Could you please confirm whether the team is planning to fix the status bar and navigation bar issues in an upcoming update?
Yes. There are a bunch of other changes regarding edge-to-edge, and we should hopefully get rid of the warnings in Play Store too.
Yes, the first two at least.
@Kanishka_Developer this should be fixed now, can you update the built app and try it?
Some of the other changes may affect some spaghetti and workarounds my UI uses. I will try to test and get a build out tomorrow.
2 posts were split to a new topic: There is still a problem when trying to change the status bar and navigation bar colors
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.




