Can I open an AppyBuilder project .aia file in Thunkable?


Can I open applybuilder project .aia file to thunkable any one know about this please reply.


why not try it by your self?


Actually I am working on my project from 6 month but after creating full project my Application forced stop in phone. My application size is 6MB and I use very low Kb images in my application. I am not getting any solution in applybuilder to resolve Forced stopping problem.


Images in Kb doesn’t tell me much as they could still be big in pixels…

Have you asked for help before, as well as showing your code…



My application codeing ? Sorry but i don’t want to share my application’s coding. Can you tell me why force stop problem come in applybuilder application ?


This is the same as going to a doctor and telling him you are sick and he has to cure you without telling him what your symptoms are.


If I’m going to guess what might be wrong,

  1. then it’s probably your images that are too big
  2. your code makes your app go in a loop and crash
  3. etc

without further information such as

  1. image size in pixels
  2. and possibly related code

otherwise nobody can help you



And the big list by SteveJG what may be wrong…

Developers most frequently have the following issues that create issues when live developing or creating the apk (compiling)

  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. Your source file (the aia file) is larger than the 5Mb limit allowed in AI2 (the aia can not be larger than 5Mb/10Mb). You may have put images or other resources in your Media (resources) that you do not use in the app. All the images and sounds in resources count toward the 5Mb limit along with the source code. You can program apps larger than 5Mb in the browser, but the apps will not compile and might not run in the emulator or the project may not save as an aia. If this is the case you need to reduce the size of your image and/or sound files. Most image files can be made quite small by resizing them using a photo manipulation program on your PC to less than 50Kb each.

  3. You might have more than 10 Screens in your app. AI2 frequently becomes unstable when more than ten 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 11th Screen.

  4. You might have set a Screen icon in the Designer Properties for your project that is too large. Use an image size of 48x48 px or 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).

  5. You did not code the entire project using App Inventor 2. If you used one of the third-party AI2 clones,you might not be able to load a Project into the AI2 compiler or create an apk with the standard AI2.

  6. If you incorrectly modified the project’s Manifest files using a third-party tool, you may have issues returning to MIT App Inventor.

  7. 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.

  8. 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 MIT server a few minutes later will give you a more favorable response.

  9. Do you have BlueStacks on your PC (BlueStacks is a special emulator that allows Android apps to run on a PC)? The Google emulator on AI2 cannot run unless BlueStacks is disabled and all of the BlueStacks processes are shut down. On a Windows PC, you use the Task Manager to ‘kill’ running processes.

  10. Are you using Sensor controls (except for the clock)? Most Sensor controls or controls related to sms or the phone do not work in the emulators. This includes the LocationSensor and Accellerometer. These components need to be tested on a device.

  11. If this is an issue about the Project loading slowly on your device or on the emulator: Be aware, the more images, layouts, components you have on a screen, the longer it takes for the emulator and Companion to render the graphical screen. How fast the emulator renders is partially a function of your hardware…how much ram you have, your cpu clock speed etc. Sometimes, with lots of graphics, the emulator will just give up. Can you develop live using WIFI or using USB? These options almost always render faster than the emulator but will not be at lightning speed if you have lots of graphics. Be patient.

  12. We have seen instances where it is probable the Google Cloud messed up; other instances where an older PC has had memory issues and caused file corruption of the Project and instances where a user is using a very slow Internet connection (like dial-up) and it is just too slow.

  13. Do you have an AVG, Eset or AVAST virus checker. Some versions of these products have been reported inhibiting/ running the emulator unless (in the case of AVG) the Advanced Link settings on the software are set to allow AI2 communication.

  14. 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.

  15. Having issues getting AI to run at all, perhaps your firewall is blocking. Don’t turn your firewall off, just allow AI2 to pass unhindered…some firewalls have the ability to allow or deny certain urls.

  16. If you get a build server busy … It is possible the buildservers may just well be busy! If you get this message, just try the build again. MIT currently runs 3 buildservers all the time. They occasionally add a 4th or even a 5th. There is a load balancer which distributes work to the buildservers. If you get the “busy” message, either the load balancer could not find a buildserver with available resources or the the buildserver it assigned the request to decided it was too busy. The solution is to just try again, either immediately or in a few minutes. If this message persists, then something might be broken and you can report it on the forum. If something IS broken, MIT will find out about it soon enough!

  17. If you have excessive resources and suspect that might be causing problems, you can look at what is in the emulator. In both in the Companion via WiFi and in the emulator, with the emulator “up” you should be able to go to: on the PC running the emulator. Going to that url should show you a small (possibly empty) directly listing (it will be a list of the assets that are used in the emulator). If you do not actually use a file in your app, make sure you remove the files, images etc. that are not being actually used. These files bloat your program.

  18. 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.

If the connection times out, that is a problem! The aiStarter program uses the “adb” program (in the “commands-for-AppInventor” folder) to setup “tcp port forwarding” from the PC to the emulator on port 8001. This command could be failing for you. Make sure you don’t have security software that is blocking the action of the “adb” command.

  1. The problem could be something else, like running an old version of Companion …if this is the case the cure might be if you are using the emulator: Projects > Hard Reset. A pop up should appear (if no issues, nothing will happen…just smile). However, sometimes you need to close your browser and reload your project to update Companion with the emulator. When the pop up appears, follow the instructions very carefully, then reboot your PC and try again. Yes, Companion on your device must be the current Companion if you are developing live on a device.

  2. If this is a connection issue with WIFI: If the device is set up to be used with USB, the Android cannot be used with WIFI unless the Settings > [developers options] in the Android box next to USB debugging is unchecked in the device.

Some users try to use their phones BOTH with USB and WIFI. That can be done. To use the live development USB option the developer must have the USB debugging box checked. If developer later wants to use WIFI the USB debugging box should NOT be checked. If you switch from USB and then to WIFI, you may have to close and restart your browser to release cache items that tell App Inventor your are connected to USB or WIFI when that is not the case.

  1. Parse Error: The most common cause of a parse error is the device has run out of storage. Do you have lot of apps on your emulator? or Device? Try freeing up space there (clear the TinyDB perhaps-TinyDB.ClearAll), and see if that helps.

A second type of parse error may occur while attempting to update the emulator: When I got the “parse error” message in the emulator, I fixed it by…

  • uninstalling the tools via the Control Panel
  • rebooting
  • re-running the install file, but this time by right-clicking on it and running as an administrator
  1. Do you have lots of Windows open on your browser or are you streaming music or video?

  2. Large bmp files ( 1 to 2 MB in size, 800 x 1500 pixesl) loaded into a button that is 50 x70 pixels will cause Companion to fail when loading a project. The issue is AI2 must compress these images to the small size to make them fit in the small area. The solution is to make these files 50 x70 pixels (or however large they must be in on the Android). Instead of bmp files, use jpg or png files. Consider png image files may not be as sharp as jpeg images but the png files scale better to different size screens.

  3. ai2 reports "Server error. Could not save one or more files."
    Clear your browser’s cache. Close the browser, then load it again. Try to build again. Sometimes switching from Chrome to Firefox or Safari or the reverse performs a miracle and corrects an issue related to the browser cache. Microsoft’s Edge might seem to work for you, however our experience is it sometimes fails while the recommended browsers do not.

  4. for extension developers: The current best practice is to have a package per extension that contains all classes required for the extension so you may want to split up your classes accordingly.

  5. Several very different things seem to evoke the package installer has stopped message.1) Using a app icon larger than 48 x 48 pixels (the png or jpg image you use to identify your app on a device set on the Designer screen). will evoke this issue. Use a 48 x 48 jpg or png image. This is a very frequent issue that evokes the error.2) Removing unused files from Media (even though the aia is less than 5Mb) has cured the issue.3) If the apk installs on other phones, but not this one perhaps there isn’t sufficient space on the phone. If the apk installs on other phones, it is not an issue with the apk. You may have too many apps on your device.

  6. Does the app work in Companion but not run the first time the apk is installed? If you use a TinyDB and set a default to empty instead of 0 on first run of the TinyDBy (initially the tinyDB contains no values)there might be a problem with the app until values are added to the TinyDB.

  7. 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.

  8. Are you developing an app to use on both tablets and phones using a large screen tablet? Ensure you check what the app will look like on the smaller device early in your screen design process or …well, you will find out.

  9. Before finishing a project, build the apk several times and test on a actual device. Some programming bugs only manifest themselves in the compiled version. This is frequently the case when building apps with many screens, many layouts, many large image or sound files. Build an apk early, especially if you have a large Project and shield yourself from a huge problem. If your app is going to crash, find out early in your development process.

  10. Developing multiple Projects using the emulator and a TinyDB? Unless you occasionally use the call TinyDB.ClearAll block to free the TinyDB memory that is stored in the emulator. If you store a lot of data, you soon will cripple the memory allocated to the emulator and that may cause problems.

  11. When developing using the emulator and TinyDB and working with multiple Projects, try to avoid using the same tags in each Project or you might find yourself wondering why data from ProjectA suddenly appears in ProjectB. If you use a tag in ProjectA like messages and use the same tag in ProjectB, you will have issues.



“Let the Guessing Games begin!”

If you can’t solve your problem by yourself and ask for help, then you have to expect to provide some information about your app. If not, read the list @Boban_Stojmenovic provided and good luck.

In your situation, I would start mentioning WHEN does your app force closes. When doing what? When your app starts? When touching a button? When opening another screen?
Then maybe you will only have to show that part of your blocks. Besides, we don’t really want to check your whole code. Most of us we don’t have that kind of free time.

About migrating to Thunkable, why don’t you just try it? You will not lose anything in AppyBuilder.
But keep in mind that you will have to remove every component that is particular to AppyBuilder. If I were you I would try to solve it and stay in one platform.


@Boban_Stojmenovic great information. We’ll add it it thanks


Oh, and another thing. If your app is force closing because of something you did wrong in your code, it will still force close, regardless of the distro you use to build your apk.


hi u can easily remove the admob components and use it on thunkable,
i have already done it thanks,


It’s not just the Admob component. There’s a lot of thing that exist only in AppyBuilder. The simplicity of migrating depends mostly on how many of those unique components/properties are in his/her app.


the first thing you might want to do is to follow tip 1 and 2