An exact copy of a working AIA and app (apk), builds a non working APK

[appsbeheerder]

Thanks Italo for the clue of a missing line in the manifest (Boban).

< category android:name=“android.intent.category.LAUNCHER” />

Since I did not change the manifest, it is a riddle why this can be the case. I can decompile it and see if this happened. Meanwhile I have taken an earlier version and made the changes again. It compiles and I can make version copies. I know an ugly solution but it worked.

[Italo]

I had the same happening a couple of weeks ago.
Glad it worked.

[Italo]

The problem seems to happen when you make a “SAVE AS” of your app.

[yanquisalexander (Alexander Barrios)]

Well, if it is considered a mistake they should report it on GitHub

Report issues and request features on our new GitHub issue tracker

We get hundreds of bug reports and feature requests here on this community, whilst we do try to take note of as many as possible internally, some can be missed and there’s no way for users to see the progress/status of these issues. Using GitHub issues, we can add labels, milestones and keep you updated on the progress of the issues. You can find the Issue Tracker at: You will need a GitHub account in order to create an issue and issues must follow the templates provided.

[Boban (Boban Stojmenovic)]

happen when you make a “SAVE AS” of your app

This was a strange one, haven’t hade this kind of issues

Btw, If you experience this at any time please post a demo.aia of it

[Italo]

Have you tried this too?

My Kodular app doesn't seems on device after downloaded

Thanks for your early post, but just now I have done it another way: Just open the AIA file in WinRAR and find the Screen1 and open that in Notepad file and delete the name as shown in the blow image. [00] [1] [2]

[Italo]

That’s what happened to me and I found this solution which worked perfectly:
And @pavi2410 knows about it. May be there wasn’t time to fix it yet.

My Kodular app doesn't seems on device after downloaded

I found the issue (It’s related with… )

[Boban (Boban Stojmenovic)]

But this should not happen anymore as long as you don’t have a old aia file from makeroid time

[Italo]

In my case it happened the Koduloid game, which I started recently. And I never made an app when it was named Makeroid. I made a copy of it and when I tried installing the copy, the installation went OK but I couldn’t find the app anywhere, except in the Apps Settings.
I downloaded the aia, made this change from @7StarMedia and re uploaded it. After that the apk installed perfectly.

[Boban (Boban Stojmenovic)]

I would like to replicate this behavior but so far no luck

[Italo]

I’ll try doing what I did.

[appsbeheerder]

It is awful but again the same error is risen. My working aia and apk can be saved as a checkpoint, but the result of the copy will produce a non visible app. Checking manifest.xml the line < category android:name=“android.intent.category.LAUNCHER” /> is missing.
But I just copied a working file without any changes in Kodular.
What to do Boban because of this erroneous behavior?

[Boban (Boban Stojmenovic)]

Since @Italo experiences this with a new project however, I have to ask is it old or new

What to check, download you aia, open it with 7-zip or equivalent program

Check that you have only kodular folder, if you have ex. makeroid then move all files from it to kodular and delete makeroid folder

Go to \youngandroidproject\ folder and open project.properties.xml, check that it contains io.kodular as in the folder structure above, if not change it

As I mentioned the big post

Can't/Won't Open App, Button Disabled After Install

You can try all these solutions but the easiest is perhaps if your buddy who can upload the project in their account or if you have two account’s you can do it yourself

[appsbeheerder]

I made this Kodular app from scratch in Kodular.
Checked the apk and there is no makeroid folder at all.

[Boban (Boban Stojmenovic)]

Checked the apk

Check aia file

[appsbeheerder]

No sign of makeroid in aia project.properties

main=io.kodular.appsbeheerder.WoordSpel_v28.Screen1
name=WoordSpel_v28
assets=…/assets
source=…/src
build=…/build
icon=WoordSpel_logo.png
versioncode=28
versionname=1.0.28
useslocation=False
aname=WoordSpel++
sizing=Responsive
showlistsasjson=True
packagename=com.appsbeheerder.woordspel
onesignalappid=xxxxxxxxxxxxx
color.primary=&HFE5A72D5
color.primary.dark=&HFF303F9F
color.accent=&HFFFEC007
theme=AppTheme.Light
splashEnabled=False
splashIcon=TaalSpel.png
minSdk=19
rtlSupport=False
projectColors=[{“hexa”:“B2A4D8FE”,“freq”:“1”},{“hexa”:“8E9EA4FE”,“freq”:“1”}]
receiveSharedText=text,

[Boban (Boban Stojmenovic)]

Sorry I’m clueless

[appsbeheerder]

It seems that decompiling apk, adding < category android:name=“android.intent.category.LAUNCHER”/ > and (App2market) compiling it, is the only solution for now. A lot of extra steps, but if there is no other solution, it is.
I wholeheartedly hope, it is the only project that will show this behaviour.

Thanks Italo

[Italo]

The only way of making backups I use is downloading the aia and adding the reversed date to it (for better sorting), like MyAwesomeApp_20200110.aia.
Checkpoint and Save As are too buggy at this time.

[appsbeheerder]

@Boban

You can try all these solutions but the easiest is perhaps if your buddy who can upload the project in their account or if you have two account’s you can do it yourself

This option worked for me. My project uploaded in another account (Boban thanks) and exported. The exported aia loaded in my account and the built apk is perfectly oke, including visibility in the launcher.