Intermittent build problems on ai2.appinventor.mit.edu

[Evan Patton]

Hello everyone,

We are aware that there are some ongoing issues with building larger projects on ai2.appinventor.mit.edu. We are working to localize the source of this issue. In the meantime, you should be able to build larger projects using the code.appinventor.mit.edu. We will update this post when we have more information.

UPDATE (2018-09-21 16:56 EDT): We have deployed a potential solution to the build problem. If you are still unable to compile your apps due to timeouts, please let us know.

UPDATE (2018-09-21 18:08 EDT): The "fix" we deployed has alleviated some build failures, but doesn't completely solve the problem. We are working on some alternative approaches to further improve the communication between AI2 and the build servers.

Regards,

Evan

[Abraham Getzler]

(added to App Inventor Issues section of FAQ)

https://groups.google.com/forum/#!msg/mitappinventortest/wqJin0qO8M0/8xUafdROAgAJ

ABG

[BodyMindPower]

But the current version of code.appinventor.mit.edu uses compileSdkVersion = 22, NOT compileSdkVersion = 26.

So that does not really help.

Therefore, my solution is first that I remove some assets from the aia project and create the apk. Then I decompile the apk (AppToMarket or APK Studio / apktool) and add the missing assets again.

Anke

[Chris Ward]

Hello Anke

Another way is to store the assets on your own web server and have the App download them on first run. This reduces the APK install time, a good thing because if it takes "too long", some Users will think it has failed and abort it.

[Bruno Bueno Mena]

I want to report a problem, maybe it can help your team:

2 notifiers are showing in a row now in my app that didnt happen with previous compilations,

a) Runtime Error

invoke: no method named "Get value" in class java.lang.Boolean

END APPLICATION

b) Problem with application

cannot find the component screen10

The screen 10 is actually the second of the app but I named like this.

They occur when I switch screens.

[Chris Ward]

Hello Bruno

It is possible that your issues are not actually related to this post. They sound like a problem with Screen management or potentially another logic issue in your Blocks. Do you want to share your Project File with us to see if we can find the cause of the problem?

[Bruno Bueno Mena]

Well its the app I'm selling in Google Play, and it had no issues with

screens before the new compilation.

If there's a way to send it to you privately I'd agree.

[Chris Ward]

Hi Bruno

How about a Test app which is basically your App - same number of screens and same screen management, but without any of the GUI or Code meat and potatoes?

Alternatively you can give MIT permission to access your project from the Server.

[Bruno Bueno Mena]

Ok, you have my persmission to see it from the server.

The project is called ForLand_Companion.

I have to say that it used to work before, but now it seems

that the switch of screens and the balls and canvas from the

menu dont work properly.

If for some reason you need to download a file to test my app:

en-es B1 capitulo 3 vocabulario

you can download it inside my app.

[Chris Ward]

Hi Bruno

I have assigned your Project to MIT Guru Evan Patton. I'm sure you will appreciate that he is a very busy man, but if anyone can pin down a fault, old or new, it's Evan.

[Bruno Bueno Mena]

Ok, Im honored to be examinated by him :)

[Evan Patton]

This post was specifically for failures to build projects due to timeouts. I'll take a look at the project, but we should really move the conversation to a fresh post rather than post hijack. Bruno, please open a separate discussion for your issue.

Regards,

Evan