Please test tonight's update

[Abraham Getzler]

Here's the test announcement for tonight's update, if you want to test directly ...

We are testing the next release on ai2-test.appinventor.mit.edu. This is a bug fixing release that addresses the following issues:

* ActionBar presence is now tied to the theme. Classic will provide the old title bar and new themes will use the ActionBar.

* Updated CompanionUpgradeHelper to fix a crash when upgrading the emulator.

* Added a check for Mac OS X 10.13 High Sierra warning about incompatibility with the emulator.

* Fixed a crash when tapping on the ActionBar menu button.

* Fixed an issue where the titlebar would not hide in the Classic theme.

* Fixed an issue where themes on some versions of Android were not styled correctly.

* Fixed issue where Markers with percent width/height would prevent project loading.

* Fixed an issue where a trailing comma in the permissions list of an extension would result in a compiled app that would be rejected by Google Play Store.

There will not be a new companion with this release. Please help us test. We would like to release this version tonight as it addresses some critical issues that users have encountered since the Dec 27th update.

 

Yes, it would be good to share this with individuals having problems with the current version of CompanionUpgradeHelper. Note that they will need to do a Hard Reset to wipe the emulator before performing the upgrade.

Regards,

Evan

ABG 

[fishingjr]

I exported my working app and then imported it to the test server...  When I try to build and save the apk to my computer, I get this error... "App Inventor is unable to compile this project. The compiler error was".

The progress bar is at 0%.

There is also a popup that says something about Yail...

I get this same error also with build to QR Code.

I'm using the Classic Theme. Show Status and Title visible both checked.

Hope this helps... :)

[Daniel L. Metzger]

Having exactly the same issue. 

[fishingjr]

OK, I don't know if you guys fixed something or something I did...  I closed Chrome, then opened Chrome and went back to the test server...  I had other apps on the test server that were old versions.  I opened one of my other apps and it did Build.  Then I went back to my app that would not build and opened it.  It now builds to QR Code and to an APK to my computer.  I tried it several times and it worked every time.

I then installed the APK to my phone.  Seems like all my issues with the Themes are fixed.... The 3 dots do not cause a crash anymore!!!  My Title is visible and using Classic theme.  

Thanks for all the work you guys are doing!!! :)

[Reifi Soetedjo]

Thank you ..thankyou...thank you.....Please update as soon as posibble...

[Riccardo Risi]

Hi all,

when you click on three dots to the right lower angle of the screen, it doesn't show the buttons "Stop the app" and "About the app" and the app crash immediately.

The problem is the same of the previous release.

Regards

Riccardo

[Farzeen Harunani]

Please make sure you download the test version of the Companion. Riccardo, this was happening with the test Companion?
Farzeen

[Evan Patton]

Hi Riccardo,

Which version of Android are you running on your device?

Regards,

Evan

[Evan Patton]

The issue where apps won't build immediately after importing to ai2-test should be resolved.

Regards,

Evan

[Gus]

Hello,

With this this new update, when I compile an app and install on a device, when the "settings" or 3 dots are clicked, the app force closes. So far only seems to do it when "classic theme" is used. Any help would be greatly appreciated.

[Evan Patton]

Hi Gus,

Which version of Android is your device running? This will help us narrow down the bug.

Thanks,

Evan

[bitcoin]

This last update has the same issues with webview, It is not fullscreen in some https:

[rsc]

its working, title visible issue is fixed now, but when it will be fixed in regular place

[bitcoin]

What time will be it available? please release, thanks

[Riccardo Risi]

Hi,
I use the MIT AI2 Companion release 2.46 on my smartphone.

[Riccardo Risi]

Hi Evan,
the version of android on my smartphone is 7.
The issue doesn't appear if I compile my app on your server App Inventor but there is on the official server.

Riccardo

[rsc]

old problem again: Build failed! Sorry, can't package projects larger than 5MB. Yours is 5.54MB. 

everything was ok with this last time, but now problem come back

[bitcoin]

please realease it, it should be released yesterday, I need update my apps.

[jeffrey.schiller]

The release is planned for tonight (US East Coast Time) approximately 11 hours from now.

-Jeff

[Gus]

Hi Evan,

It's happening on all of my devices, Lollipop and Kitkat and a phone with a custom rom. It does not happen while testing, it only happens when I install the app on the device. 

Thanks!

[Elliot Canipelle]

Hi,
First thanks for the good work on AI2 it's a super tool for teaching,
unfortunatly I just tested the update but i still get the problem described by BEN on https://groups.google.com/forum/#!category-topic/mitappinventortest/help-getting-connected/2AvOq9A0dW4. I did a hard reset, then update companion then reset the connection and connect to emulator again, finaly I get this error :

We didn't have that problem in the begining of december, our config in school did'nt change (Windows 7+firefox) and no security update since then...

Do others bugfixes are coming soon ? We really need the emulator...

Have a good day

[Evan Patton]

Hi Elliot,

After a hard reset, you should be able to update by connecting to the emulator on the server at http://ai2-test.appinventor.mit.edu. If you continue to get the error, you may need to delete the .appinventor folder in the C:\Users\<username> directory, which contains the per-user emulator data. Let us know if either of those actions works for you.

Regards,

Evan

[Yossi Yaron]

Hi,

Looks good!

I had a lot of problems with the previous versions and it seems that you have managed to fix them.

Waiting for the official release!

Thank you all!

Yossi Yaron

[Elliot Canipelle]

Hi Evan,

I just saw your answer; thank you for helping me. I am not in school right now, I will try your solution tomorrow, but I think i have a hint on what the problem is :
This morning I tried to connect to the internet using the browser that run inside the emulator, it didn't worked.
I had never tried this before, maybe the emulator never could connect directly to the internet even when everything worked in 2017.
It seem to me,(but maybe I am wrong) that before december when we had to update the companion the model is :
AIstarter get the update for the companion via the web browser (or directly from the internet idk) then pass it to the emulator, then we instal the update, reset...
But now the model is :
AIstarter get the update for the companionUpgradeHelper via the web browser (or directly from the internet) then pass it to the emulator, then we install thecompanionUpgradeHelper , then we reset, reboot and finaly the companionUpgradeHelper runing on the emulator dowload the new companion.
Do I get this right ? does the emulator do need to communicate directly to the server now and not use the AIstarter as a bridge?
If so, we use a proxy in school, how to configure the emulator so he could communicate outside directly ?
Thanks again for your help.

Regards,
Elliot