I also tried to install AAPT via command-line and restarting the build server but no change but still no change 
You'll need to replace the various executables in the lib/android/tools/linux directory with their arm counterparts. The versions we include in our source tree target the x86_64 architecture. Once you're replaced the binaries you can rebuild the build server.
3 Likes
Thanks for the help, can you please also tell me where would I get those counterparts?
You should install Android Studio and get them from the build-tools folder. You might also be able to install platform specific version via apt.
2 Likes
Will the things present in Android Studio's build-tools folder be 32bit compatible?
Thanks to the moving parts of appinventor, we can host the buildserver anywhere, just config that on appengine-web.xml, and done its working. But I need to host it on raspberry pi as its more convenient to host everything there.
But still for some unknown reason the build is still not appearing on the UI
Logs:
I am running the same app inventor fork latest from github but get this error 
Why my appinventor instance hosted on Pi has 
suffix?
@ewpatton I tried to host the buildserver on my pc and the build is working too but, for some reason some error is coming, log below
Check the logs on the appengine side. It's rejecting the build result from the buildserver and you should see more information there.
1 Like
Hmm, I will have a look there, however I have updated my Pi 4 to ubuntu server 64bit so I will able to host everything there
@ewpatton I thought it might be because its now 64bit but compiling need 32 bit arch, so I tried to run the command told in repo's read me, but some error came
I feel like you're mixing up too many things in order for me to help you. If you're on a Raspberry Pi still, then those versions of the libraries won't exist because it's not the right architecture. I still recommend that you should just install aapt, etc. from the Android SDK and then replace the copies in our source tree with versions known to work for your platform.
Sorry For That 
I will clear the mess now,
Machine: Raspberry Pi 4 2GB Ram
Operating System: Ubuntu Server 20.04.2 LTS
Java version: 
Ant Version: 
Some More System Info:
Problem:
Suspected Cause: missing 32 bit libs
This step doesn't rely on any native code so 32-bit libraries are not a problem. You're also running on a 64-bit machine so you'd just want to use 64-bit binaries in that scenario. You're likely running into a memory issue given that you've only got 2 GB of RAM. Do you have swap set up for paging purposes? Do you see any OOM errors in /var/log/dmesg? You could try decreasing the max memory requested for the GWT compilation but odds are Java will then exit due to not having enough heap. Consider building YaClientApp on another platform with more RAM.
I am setting that up now
I don't find it, but some errors saying memory full or something like that
How can we do that? Can I build the appinventor on PC and transfer it to pi?
@ewpatton Is this step required now as when google has replaced the google android SDK for 32bit systems?
No, and it certainly won't work on a Raspberry Pi. Those instructions assume an x86_64 arch as i386 would be the corresponding 32-bit arch.
Sorry, but I didn't understand that. Can you tell that again?