D DawningTruth Active Member Licensed User Oct 22, 2022 #1 I am trying to compile an old project which was on another machine. The new machine has the latest version of B4A (111.80). I keep getting the error below. Any suggestions? Error M3ssage: B4A Version: 11.80 Parsing code. (0.20s) Java Version: 11 Building folders structure. (0.08s) Compiling code. (0.51s) Compiling layouts code. (0.04s) Organizing libraries. (0.00s) (AndroidX SDK) Compiling resources (0.07s) Linking resources Error res\mipmap-anydpi-v26\ic_launcher.xml:3: error: resource mipmap/background (aka b4a.example:mipmap/background) not found. res\mipmap-anydpi-v26\ic_launcher.xml:4: error: resource mipmap/foreground (aka b4a.example:mipmap/foreground) not found. error: failed linking file resources.
I am trying to compile an old project which was on another machine. The new machine has the latest version of B4A (111.80). I keep getting the error below. Any suggestions? Error M3ssage: B4A Version: 11.80 Parsing code. (0.20s) Java Version: 11 Building folders structure. (0.08s) Compiling code. (0.51s) Compiling layouts code. (0.04s) Organizing libraries. (0.00s) (AndroidX SDK) Compiling resources (0.07s) Linking resources Error res\mipmap-anydpi-v26\ic_launcher.xml:3: error: resource mipmap/background (aka b4a.example:mipmap/background) not found. res\mipmap-anydpi-v26\ic_launcher.xml:4: error: resource mipmap/foreground (aka b4a.example:mipmap/foreground) not found. error: failed linking file resources.
Erel B4X founder Staff member Licensed User Longtime User Oct 23, 2022 #2 In most cases such errors are related to a misconfigured Android SDK. Delete it and download the two components: https://www.b4x.com/b4a.html Upvote 0
In most cases such errors are related to a misconfigured Android SDK. Delete it and download the two components: https://www.b4x.com/b4a.html
D DawningTruth Active Member Licensed User Oct 24, 2022 #3 Thx Erel, I did reload the SDKs. Turns out the issue was caused by the icons for the app. I had to delete the icon files and it worked. Looks like I will have to recreate the icon files again to be in compliance with the latest standards. Upvote 0
Thx Erel, I did reload the SDKs. Turns out the issue was caused by the icons for the app. I had to delete the icon files and it worked. Looks like I will have to recreate the icon files again to be in compliance with the latest standards.