I tested it with a Pocophone F1.
The same error.
Other cell phones are not available to me.
Frank
I tested it with a Pocophone F1.
The same error.
Other cell phones are not available to me.
Frank
I wrote down my complete configuration. Maybe someone will spot an error.
Windows:
Windows 10 pro with all updates
browser:
Firefox 110.0, also tested with Firefox portable 110.0
MIT App Inventor:
Built: January 30 2023 Version: nb190c
Use Companion: 2.65 or 2.65u
Target Android SDK: 31 (Android 12.0)
installation:
MIT_App_Inventor_Tools_2.3.0_win_setup.exe
aiStarter:
App Inventor version: 30.265.0
Architecture: AMD64
ADB path: C:\Program Files\MIT App Inventor\from-Android-SDK\platform-tools\adb
Bottle v0.12.13 server starting up (using WSGIRefServer())...
Listening on http://127.0.0.1:8004/
smartphone:
Xiaomi 11 Lite 5G NE
App on smartphone:
MIT App Inventor 2
Version: 2.65u
error messages:
1st message:
Error from Companion: java.lang.RuntimeException: invalid syntax in eval form: :12:1:
caught exception in inliner for # - java.lang.RuntimeException: no such class:
see above (first post)
2nd message (sometimes):
Runtime Error:
invoke: no method named `GetValue' in class java.lang.Boolean
Note: You will not see another error reported for 5 seconds
View of the app on the smartphone:
white Screen without any Buttons etc.
Frank
I suggest using a more modern emulator from
and dragging a fresh current Companion into it if needed.
Sorry I don't understand your answer.
I use version 2.65u on the smartphone.
Isn't this up to date?
Frank
Your smartphone is up to date.
Your emulator might not be up to date., in its Companion or its O/S.
The stock MIT emulator can't run some projects.
Can you please send me a link to the current emulator.
If possible a 32bit version.
Thank you very much.
Frank
This is a more recent emulator
but it needs a sideload of the latest Companion:
http://appinventor.mit.edu.ezproxy.canberra.edu.au/ai2/ReleaseNotes.html
see FAQ Section: Companion and Emulator
for other emulator options.
I think this might be an issue with the USB connection, but I need to investigate.