APK generates, but app doesn't work

Looking at the dates, it seems that all my issues, plus the apk issues, seem to have occurred following the recent update of kodular to Version 1.5C.0.

1 Like

Things are definitely wrong, specially with communication from the devs. I guess it wouldn’t hurt just to acknowledge and say “we’re working on it”.

Hope someone from the team can step up and say something. But I guess we had it comming when we signed for a free service.

1 Like

I paid for this service with a premium account, specifically because I thought it might provide a better service.

Right now, I cannot do any app development as the layouts are screwed in my apps and I can’t build anything new in an environment that’s not working correctly, not least as I may have to change them again when (if) it’s fixed.

I had wondered if it was an extension issue, but it’s definitely not as it’s happening with kodular components as well. In my case, with the broken layouts heights (and widths too, I’ve just discovered) the update must have broken how the screen sizes are identified or how the app responds to them etc.

I’m now left with every single backup I have of the app - about 80 different aia files - stretching all the way back through its development, not working correctly. That’s a pretty big bug in the update and surely I cannot be the only person seeing layout errors and glitches since the update?

2 Likes

You face this problem when installing the application it does not work on these components

It looks exactly like what is hapening to me.

Have you had any luck after removing any of the extensions?

This isn’t just you, I and everyone here are also experiencing this… maybe it’s being fixed by Kodular.

2 Likes

14 posts were split to a new topic: 206 screens, app not working

You could use logcat to find out more

Taifun

Thank you for writing this howto, I didn’t know that.

I have the same problem, the app runs only when I remove the firebase authenticaition component

Is it possible that we have to delete the authentication component, then re-enter the component with a new j.son?

I tried it but it doesn’t work for me :pensive:, I’m testing if there may be a conflict with another extension but I still can’t find it.

its all a red-herring. Kodular is STUFFED!

1 Like

Can’t target Android 13 (API level 33) or higher /Can’t download APK Also let me know if you get a solution

exactly!!!

1 Like

My service is paid (premium) and the same thing is happening.

1 Like

Removing the extensions does not solve the problem. I did a test and removed all the extensions I use and the problem continued. Sad.

1 Like

If you want to share your AIA privately I can review it

I have a project that was working perfectly before the Kodular update, now it gives me this error and does not run:

It has nothing to do with the Firebase authentication component since it is not added

The Kodular team should seriously consider restoring the previous version, users had already found ways to update to API 33. They have only harmed the work of many people by updating the platform without doing adequate testing.

4 Likes