Error compiling example project in LAMW lazarus / 43-Android ---------------------------------------------------------------------- Lazarinr · 2025-08-11 04:05 When I create a new project in LAMW, it compiles normally without errors. However, when I compile a project from the demo folder, this error occurs. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i MessagesVerbose: Selected chip architecture: armeabiVerbose: Taking libraries from folder: C:\lamw_manager\LAMW\lazandroidmodulewizard\dem os\GUI\AppClockDemo1\libs\armeabiProject: Executing command before: Successbefore build...Compile Project, OS: android, CPU: arm, Target: C:\lamw_manager\LAMW\lazandroidmodulewizard\demos\GUI\AppClockDemo1\li bs\armeabi\libcontrols.so: Exit code 1, Errors: 1Fatal: Cannot find system used by controls. Make sure all ppu files of a package are in its output directory. ppu in wrong directory=C:\lamw_manager\LAMW\LAMW4Windows\fpc\3.2.0\units\arm- android\rtl\system.ppu..Exception, Errors: 1Fatal: [Exception] Failed: Cannot build project ---------------------------------------------------------------------- nicelybrewed · 2025-08-11 06:04 Check that the project is set to the correct chipset to match your device, it looks like it's set to ARMv6, most likely needs to be Aaarch64 or ARMv7a+VFPv3 depending on your device, in Project Options > [LAMW] Android Project Options > Build. ---------------------------------------------------------------------- Lazarinr · 2025-08-11 11:53 Thanks for your help, @nicelybrewed. I did as you suggested and it fixed the error, but now it displays another error. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Messages, Hints: 2Verbose: Selected chip architecture: armeabiVerbose: Taking libraries from folder: C:\lamw_manager\LAMW\lazandroidmodulewizard\dem os\GUI\AppClockDemo1\libs\armeabiNote: Duplicate unit "controls" in "controls", orphaned ppu "C:\lamw_manager\LAMW\lazandroidmodulewizard\ demos\GUI\AppClockDemo1\obj\controls\controls.o"Note: Duplicate unit "controls" in "LCLBase 3.8", ppu="C:\lamw_manager\LAMW\LAMW4Windows\lazarus_trunk\lcl\units\arm- android\controls.ppu", source="C:\lamw_manager\LAMW\LAMW4Windows\lazar us_trunk\lcl\controls.pp"Project: Executing command before: Successbefore build...Compile Project, OS: android, CPU: arm, Target: C:\lamw_manager\LAMW\lazandroidmodulewizard\demos\GUI\AppClockDemo1\li bs\armeabi-v7a\libcontrols.so: SuccessProject: Executing command after: Successafter build...Building APK (Gradle)... : FAILURE: Build failed with an exception., Errors: 1Fatal: FAILURE: Build failed with an exception.* What went wrong:Execution failed for task ':processDebugMainManifest'.> Manifest merger failed : android:exported needs to be explicitly specified for element . Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity- element#exported for details.* Try:> Run with --stacktrace option to get the stack trace.> Run with --debug option to get more log output.> Run with --scan to get full insights.> Get more help at https://help.gradle.org.Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.You can use '--warning- mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface. html#sec:command_line_warnings in the Gradle documentation.BUILD FAILED in 6s15 actionable tasks: 15 executedWatched directory hierarchies: [C:\lamw_manager\LAMW\lazandroidmodulewizard\demos\GUI\Ap pClockDemo1]Exception, Errors: 1Fatal: [Exception] Failed: Cannot build APK! ---------------------------------------------------------------------- nicelybrewed · 2025-08-11 12:31 This is because the demos were created prior to Android 12, and LAMW I defaults to targeting a higher API than Android 12,  you could also reduce the 'Target SDK Version' to 30 (Android 11) for testing....or amend your demo, like below: The Androidmanifest.xml file in the root of that demo needs adjusted slightly to include the android:exported option in the activity element like: Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i     Notice android:exported="true" has been added to the end of this line, It should compile/run after that change, you may find other demos are the same. ---------------------------------------------------------------------- Lazarinr · 2025-08-11 13:01 Solved! Thanks for the contribution @nicelybrewed. ---------------------------------------------------------------------- nicelybrewed · 2025-08-11 13:05 No worries.