Program will not compile, DX execution failed

MIT App Inventor Help
1

Hi!.
I've added yet another web component and my app does not compile (see error below) while it runs in Companion. AIA size is 1057kB. It hase several extensions (I started to build extensions so to lower number of blocks on main screen - now 8100. 6 screens, remaining much smaller.
Any help appreciated

v86failed
v86failed941×598 88.5 KB

Regards
Kuba

2

Please do a search for DX execution failed here in the community. You have too much of something (by @Boban ) in your project

Taifun

1 Like
3

Thanks @Taifun.
Of course I've searched Community 1st and read that article and none of specific conditions apply.
By asking this question I hope somebody has found:

a) how to find what to reduce how extensions count agains blocks what is reasonable limit of resources (as e.g. I tried to build extensions in Niotron to limit number of block on Screen1 at 8k i.e. well below 10k and to reuse code between screens)

b) a way out. eg. local server, wait next release we are optimising, choose test server at ...

c) Maybe I've used AI2 past it's purpose and for my purpose AI2 is blind-end and I must migrate to AS/Flutter before I can do next release ? Hope not.

Regards

4
  • make a copy of your Project
  • delete a Screen and try to compile your Project, if it compiles smile you found the issue, if it does not compile, try again with another Screen.
  • keep trying to eliminate the issue.
  • if all fails, share your code and someone might help debug. or consider using virtual screens.

73,
Steve

5

Follow the DRY principle and reuse your blocks and components, use procedures and the advanced blocks... also seperate data and logic

Taifun

6

Dear @SteveJG
Will do. Thanks!
73
Kuba, SP5NZF
BTW If u share gmail address of yr phone, I'll be happy to invite u to internal tests of this logbook

7

I see your project name is Simple HAM Logger.

I imagine you are inputting and accumulating data, maybe from text boxes.

Do your display components grow as your data grows?

8

Thanks for asking dear @ABG.
This amateur radio logbook storing (and viewing, exporting) data in sqlite db.
The aia package is 1.1MB comressed.
Inside, there are assets consisting of 20 extensions (uncomressed ca 700kB) couple of png's (one big 129kB I can size it down) and 3 text files - all assets (including extensions) are ca 1MB uncomressed.
Screen controls (lists) are max 15 entries long and other text boxes keep short texts (most of them under 20 chars) and it did not change for a while.
Dynamically some lists grow big when fed from external web sources but it is nothing in compile-time.

Latest (breaking) change was adding to Screen1 ca. 100 blocks and 1 web object (4th instance of standard web component but to keep OnGotText event handlers short and because I can't tell if for same url it returns result of GET or POST I keep them separate). Screen1 has now 8175 blocks.

There are 5 other screens having 1300, 1300, 13, 322, 1870 blocks respectively.

Regards, Kuba

9

Dear @Taifun ,
I try but AI provides no way of DRY between screens. I can only copy blocks or make extensions (this is the way I've chosen for pieces tested and stabilised after a while).
Best regards, Kuba

10

Show a screenshot of what you are talking about...
And never copy blocks, use 1 screen and some logic instead

Taifun

11

If you do a lot of sorting and searching in your app, there are more compact ways to do that in nb191 with the map/reduce list blocks.

There should be no need for extensions that do sorting.

12

Thanks @ABG
I do not use extensions for sorting/searching.

13

It does - you can use Virtual Screens.

When we define virtual screens, we use one 'real' App Inventor Screen (most often Screen1). Screen-sized Vertical Arrangements on it are displayed/hidden as required - they are the Virtual Screens. This is generally a better approach for multi-screen Apps, they share data without having to "pass" it between screens and it also reduces code duplication, making the App more efficient and the code easier to follow if you have to return to it at a later date.
So, instead of separate "houses", virtual screens are "rooms" of the same "house".

I'm working on a large program with several virtual screens and a massive list of images in Assets - 1490 Blocks, 3.75 MB Project file, 7.17 MB APK

There must be some room for optimization in your code blocks.....

Also, are there any unnecessary features? Things that do not contribute to the core mission of the App?

14

You can also use tables loaded from Media to control your app:

Also, HTML and Javascript can soak up some of your block logic, using the WebViewer.

1 Like
15

Can you explain the purpose of your own extensions more in detail... there might be alternatives for doing the same functionality

Taifun

1 Like
16

Sorry for posting so late but I did my homework.
Thanks again for all hints, comments and questions that inspired me to find fix (I hope).
Finally:
The only aspect that did seem to cure DX execution failed (in my case described above) is lowering Screen1 number of blocks below 8000.
Complexity, number of objects, number of extensions, number of screens (6), total blocks on all screens did not seem to matter.
My fix was to remove over 500 blocks used in constants definitions by:

  • Load (lengthy) dict driving sqlite databes automatic upgrade to resource files (JSON) and load it when upgrade runs,
  • Have all needed config dicts in config file/db and load then on Init.

Regards, Kuba

17

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.