Hello, I imported screen and it is not open

Discuss
#1

When from another screen, I call to open the imported screen, it says error 902.
what to do from it untill resolving the problem?
the package name also isn’t correct…
photo

145
145.jpg1080×683 26.2 KB

my correct packge name is:
com.TheKingDeveloper25.diaryfinal

#2

are you sure your screen name is correct?
do you have any blocks to show

1 Like
#3

Show your blocks

This is just your package name and nothing else

bild
File structure in your apk is still this :point_up_2:

/Boban

1 Like
#4

my screen in companion works, and install it doesnt works

image
image.png1366×768 181 KB

#5

maybe this will help


@Boban you are everywhere (:

#6

I cant use custom package name at all?

#7

Now I see why

bild

/Boban

1 Like
#8

You have to manually change in your aia

/Boban

#9

I think imported screen made with earlier versions of Kodular or something, so your app can’t know the imported screen.

Can you try with empty new screen?

1 Like
#10

and what can I change manually in the aia?

#11

emty new screen always works

#12

Then as I said, the imported screen may have problems, you can move your blocks from imported screen to a new screen:

  1. Before everything, backup your project by downloading AIA.
  2. Clear your backpack by right-click menu.
  3. Copy all blocks to backpack in the imported screen.
  4. Delete the imported screen.
  5. Create a new screen and paste all blocks from the backpack.
#13

Change this the package name?

image
image.png1366×768 93.3 KB

i unzipped the ais file

#14

You can edit but I don’t know if it causes any problems when importing it.

#15

lets try it

#16

However, components will not be copied

Can’t bear to explain, PM me your aia so I can fix it for you or search in community

/Boban

1 Like
#17

Oh yes, I forgot it :man_facepalming: :confused:

2 Likes
#18

In companion it works
now i check in install

#19

ok in install it doesnt works
i will remove the pacage name

Is there any other way besides copying the code?

#20

It will be solved by changing imported screen name…