The MIT App Inventor for iOS companion app has been updated on TestFlight to version 2.74 build 24. It contains the following improvements and bugfixes:
Fix a crash in the app library feature
Improve AR capabilities (needs ar.appinventor.mit.edu)
Fix progress view animations
Fix LocationSensor Geocode causing an error on failure
Handle more error conditions in Web component
Please continue to help test as we work on bug fixes.
Cheers,
Evan W. Patton, Ph.D.
Lead Software Engineer, MIT App Inventor
The timeout, connection failure, and not connected to internet as Timeout events (an error will also be dispatched to the Screen). All other errors reported by the OS will be just sent via ErrorOccurred. The relevant patch is here:
@ewpatton Thanks for sharing this update! Really excited to see the AR improvements coming into the iOS companion. Do you happen to have any documentation or sample projects that show how the AR components work with ar.appinventor.mit.edu?
Iād also be interested in specific use cases or example projects that would let us test the other updated features (app library fix, progress view animations, LocationSensor Geocode handling, Web component error conditions). Having concrete scenarios would be great for classroom use ā and Iād be happy to test them out and share results with the community.
Over the past three weeks, I have been developing applications for iOS using MIT App Inventor.
During this process, I encountered several important limitations and issues:
When the application size exceeds 30 MB, a QR code cannot be generated and the build process gets stuck at 100%.
Audio files with the .ogg extension are not supported.
The ādo not play music in the backgroundā option is not supported.
Since MIT App Inventor 2 does not have a built-in block to detect when the screen is turned off, Appleās guideline 2.5.4 (which requires music to stop when the app is not in the foreground) cannot be triggered for music apps, and as a result, these apps are rejected. I tried countless block-based variations to solve this issue, but none of them worked reliably.
Screen orientation (landscape or portrait) cannot be locked using blocks.
It was already mentioned that nested horizontal or vertical arrangement components do not resize correctly.
Immediately after launching an app, I observed that buttons sometimes fail to grab focus, depending on the device.
In addition, while programming, it is necessary to check very frequently whether the blocks editor is still active, as the āpage refreshā warning appears far too often.
For me, the most important improvement would be the addition of a feature that can trigger an event when the screen turns off.