Failure to display one of Screens and its blocks

[Moje_3wom]

Hi

One of the application Screens design with its blocks is not displayed for me.

Instead, the same Screen (Near_me) is visible below the Screen1.

It also gives an internal error (An internal error has occurred. Report a bug?) when entering the project environment, but when I build apk, that works well. However, that Screen (Near_me) is no longer editable.

Please help without asking for the aia file.

I use 16 gigabyte RAM and Core i3-8100 CPU, and 4 mbps internet speed.
Clearing Chrome cache did not help.

[ChrisWard]

@Moje_3wom

Please help without asking for the aia file.

How can we help you without being able to study the background files that make up the .aia?

Please export your Project and upload it to this forum Topic for the Power Users to Study. We are not going to bite (much ).

[Moje_3wom]

@ChrisWard

Please export your Project and upload it to this forum Topic for the Power Users to Study. We are not going to bite (much ).

This is a precaution against my commitment not to publish it. If there is a way for a specific person to see the file. I think there is no problem.

[ChrisWard]

@Moje_3wom

This is a precaution against my commitment not to publish it. If there is a way for a specific person to see the file. I think there is no problem

We are providing free software and free technical support. If you are working for the CIA or MI5 perhaps you can ask one of your colleagues to help.

[Moje_3wom]

@ChrisWard

We are providing free software and free technical support.

With all due respect to what you are doing, I know about the greatness of what you are doing for free, and this puts you next to the elders. I apologize for the situation.

[ChrisWard]

If you are using an Extension, ensure it is up-to-date. If you have a Table Arrangement, try deleting that Arrangement (back up the Project to your drive first).

[Moje_3wom]

@ChrisWard

If you have a Table Arrangement, try deleting

I haven't table arrangement.
Near_me Screen blocks!

[ChrisWard]

You have a fair few extensions to check. It could also be something unusual in your coding - not that having a number of web components is a problem for example, but that many should not be required given that they cannot be fired at the same time.

If an extension is not the cause, then file corruption is a possibility, but we cannot help with that without studying the Project file.

You could grab a coffee and run through my checklist:
ProfessorCad: Tips & Tricks Cannot Build/Install/Run APK

[Moje_3wom]

@ChrisWard

then file corruption is a possibility

So, why build apk work fine? I tested it on my phone.

[Moje_3wom]

@ChrisWard

ProfessorCad: Tips & Tricks

Yes, I have 17 Screen. if I delete 7 Screens, it may be fixed or the effort is in vain and the file can not be repaired?

[ChrisWard]

@Moje_3wom

So, why build apk work fine? I tested it on my phone.

But it doesn't - a whole Screen is missing.

[ChrisWard]

@Moje_3wom

Yes, I have 17 Screen. if I delete 7 Screens, it may be fixed or the effort is in vain and the file can not be repaired?

10 Screens is a guideline max but in fact no App should get close to that many (10). Are some of your Screens identical in terms of components but with differing content?

[Moje_3wom]

@ChrisWard

Are some of your Screens identical in terms of components but with differing content?

Yes, It differs in terms of components and content. But their combination makes the blocks crowded.
But I have to combine a few of them.

If I delete 7 or more Screens, it may be fixed or the effort is in vain and the file can not be repaired? because these changes are hard work.

[ChrisWard]

If you really need so many screens, you will have reserved a place in the Guinness Book of Records

I would encourage you to consider using Virtual Screens.

@Moje_3wom

I have to combine a few of them.

Isn't it possible that your App simply has too many screens and components?

Golden rules in App Inventor programming:

• Optimise all images for Android
• Optimise code (e.g. use 'any component' Blocks)
• DRY - Don't Repeat Yourself
• FFB - Fat Finger Buttons
• KISS - Keep It Simple Stupid
• Test and Test again

KISS, an acronym for Keep It Simple, Stupid, is a design principle noted by the U.S. Navy in 1960.
The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided.*

- YouTube

[ChrisWard]

@Moje_3wom

If I delete 7 or more Screens, it may be fixed or the effort is in vain and the file can not be repaired?

That is the risk you have to take if you are not going to let the Forum help you by uploading your Project.

I would say that the no-show Screen possibly has corruption within one of the internal AI files that make up the AIA file.

[Moje_3wom]

@ChrisWard

That is the risk you have to take if you are not going to let the Forum help you by uploading your Project.

How good and comfortable I was.

@ChrisWard

I would say that the no-show Screen possibly has corruption within one of the internal AI files that make up the AIA file.

I just took a look at the aia file with WinRAR. I saw that the same Screen has the largest volume size.

[Peter]

What happens if you use a different browser for example FireFox?

[Moje_3wom]

@Peter

use a different browser for example FireFox

Hi Peter
As before, it made no difference.

[Peter]

@Moje_3wom

Screen has the largest volume size

And what would that be?

[Moje_3wom]

@Peter

And what would that be?

bky file 610,980 bytes
scm file 76,234 bytes