General Issues While Developing/Creating apps with AppZard

Developers most Frequently have the Following Issues that Create Isues when live Developing or Compiling the apk with AppZard.

  1. You have coding errors in your blocks. In the Blocks editor, look in the lower
    left corner of the window for the yellow and red triangle icons. If the red icon has a value larger than 0,
    you have a serious coding error. Find the block in your code that has a red triangle and fix it. Red triangles always inhibit creating an apk or running a project in the emulator or possibly creating an aia file. Yellow triangles are more forgiving, however, sometimes, these need to be fixed because they trip an internal warning and not filling puzzle piece sockets that are left un-filled can sometimes cause issues if the app needs a value that is not filled.

  2. You might have more than 20 Screens in your app. AppZard frequently becomes unstable when more than 20 screens are used. Projects can be built with slightly more screens but then you should expect your app to occasionally behave erratically. Do not ignore the warning message that appears when you attempt to load your 21th Screen.

  3. You might have set a Screen icon in the Designer Properties for your project that is too large. If your image is too large, your app will not compile. Use an image size of 96x96 instead and only use jpg or png images. *.ico files are not supported. The ‘icon’ (actually an image) Google Play requires when posting needs to be 520x520 for their display. The smaller ‘icons’ work for the app’s icon (the one shown on the device’s screen that is pressed to activate the app). For nb181 there is now provision to accept larger images.

  4. If you incorrectly modified the project’s Manifest files using a third-party tool, you may have issues returning to AppZard.

  5. Sometimes, if you have lots of Layouts on a single screen, the apk might not compile. How many is a lot? I do not know, keep adding layouts and buttons, compile and try again… when the server crashes, you got a lot.

  6. The network you use may be overloaded (possibly a school network), or you have other applications running in the background on your computer, or your virus checker is doing a scan. Sometimes, just trying to access the AppZard server a few minutes later will give you a more favorable response.

  7. Do you get the error: The blocks area did not load properly. Changes to the blocks for screen xxxxxxx_Screen1 will not be saved. One user had this error, the problem was he had too many comment boxes exposed at once for the browser to handle. Try minimizing all blocks, and opening in another browser,like Chrome or Firefox.

  8. You might have used an alpha character in the app’s Version number. The version number must be all numerical digits. Use of an alpha character will spawn a generic error message on attempting to compile.

  9. Did you use an unusual character in your apps name, or a screen name like @ or # ? Using non alpha numeric characters in these names causes compile errors. Make sure your app name or any of the screens you created uses only alpha numeric characters.

  10. You try to compile put get a variety of error messages like " AppZard is unable to compile this project. The compiler error output was" and/or “An internal error has occurred. Report a bug?” and the bug report includes this:
    foundIn = nb167el3
    faultData = java.lang.IndexOutOfBoundsException or something similar. Did you previously compile your Project using Kodular, Niotron or another third part App Inventor clone and now you are attempting to compile of MIT AppZard? The message is simple, if you choose an AppZard flavour to start your Project, stay with it. Mixing the coding is like making a cake using apples and oranges and sauerkraut. It probably is not going to work as expected.

  11. You use a reserved word for the name of a Procedure or object, that probably will cause a compiling issue. These are reserved words:

enter image description here
Make sure you always rename a Procedure when you make a new Procedure. Never use the default name ‘Procedure’.

Some Known Build Failed Errors

1) YAIL compiler - AAPT(Android Asset Packaging Tool) execution failed.

Full Error

Appzard is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating style xml
________Processing Firebase JSON
________Generating layouts
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
________Attaching Mediation Libraries
________Attaching native libraries
________Attaching Android Archive (AAR) libraries
________Attaching component assets
________Invoking AAPT
YAIL compiler - AAPT execution failed.

Solutions:-

  1. This tends to happen if there are large Images in the project.
  2. Space or Special Characters($, #, %, ! & more…) in Package Name.
  3. Images that are not Optimised for Android (Including the App Icon)
  4. Using an out-of-date extension
  5. Empty Spaces in Screen’s names when only numbers, letters and underscore is allowed.
  6. Had a space in your Project name or in your Screen1 Application Name.
  7. Not closing Screens Correctly.

2) Firebase config file error.

Full Error

Appzard is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________________Firebase components found.
________________Firebase config file error.

Solutions:-

  1. Check your json file name. It should be google-services.json and should not contain any symbols or special characters.
  2. Delete your existing json file from assets, Downlad json file again from Firebase Console and reuplaod new Downloaded json File.

3) DX execution failed.

Full Error(Similar Error)

Appzard is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________________Firebase components found.
________________Firebase config file successfully added.
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
________Attaching native libraries
________Attaching Android Archive (AAR) libraries
________Attaching component assets
________Invoking AAPT
AAPT time: 1.258 seconds
________Compiling source files
________Invoking DX
YAIL compiler - DX execution failed.

Solutions:-

  1. There maybe a Project in Project.
  2. If Project is too big(Too many blocks, screens or images).

4) Compiling source files.

Full Error(or similar)

Appzard is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
________Attaching native libraries
________Attaching Android Archive (AAR) libraries
________Attaching component assets
________Invoking AAPT
AAPT time: 0.757 seconds
________Compiling source files

Solutions:-

  1. Wrongly formatted Package Name.
  2. Project in a project (Installing Project as an extension).
3 Likes

:zipper_mouth_face:

1 Like

This is the classic explanation… Make it as globally pinned to one and all in the main screen… most of the common problems and solution was suggested… then what else.

1 Like