This error is related to the development process of your Android app, specifically the setting of the notifications icon. The error message mentions a problem with the “convert” command that is used to convert an image (likely part of the ImageMagick tool). Here are the main points:
The convert command “convert-im6.q16” reports an error stating that “no images defined”. This means that the file that the conversion command is trying to process is not properly represented or does not exist in the intended location.
Possible causes:
Missing message icon file: The file that should be used as the message icon is not provided or is not correctly specified.
Incorrect file format: The icon may be in the wrong format or damaged.
Error in your script: The script responsible for processing this icon has a problem (e.g. incorrect file path).
Solution steps:
Check the file path: Make sure the file exists and is in the correct format (e.g. PNG).
Check the script: Check the script /scripts/notification_icon.sh and make sure that it correctly references the icon file.
File format: Make sure the icon meets the Android requirements (e.g. square, transparent and the correct size).
Example: If the file is corrupted or in the wrong format, upload a new icon in the correct location. Also ensure that the correct file path is specified in the script.
The problem is very likely to be on the Adalo side, because the error is caused by the automated build process on the Adalo servers. Here are some important points that support this assumption:
Adalo’s autocreation: the Adalo platform uses scripts and tools such as notification_icon.sh to generate the necessary Android application files. Since this error occurs in the Adalo server environment, it indicates that the problem is not yours but in the Adalo autocompilation process.
Image processing error:
The script “notification_icon.sh” tries to generate a notification icon, but the image is not processed properly due to a missing or corrupted file.
Since this file can be generated or processed by the Adalo server itself, the problem is most likely in their autogeneration script or in the tool used (e.g. ImageMagick).
Adalo infrastructure:
If a file has been properly uploaded and set up via the Adalo platform, but the error still persists, this indicates that the problem is in the Adalo file management or generation mechanism.
Adalo users often report similar problems due to server inaccuracies or configuration errors.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.