Got this error "java.lang.RuntimeException: no such class" when import extension

[Kevinkun]

So is there any error when you import other extension, without import CompCreator?
If yes, then maybe I need move your post to a new thread.

[Ove_Halseth]

Yes, all components. So will start new thread👍

[ChrisWard]

After importing, you must drag the extension into the Designer, on top of the Designer background (image of phone) and it will snap to a row below the image - after that, the extension is installed.

[ChrisWard]

Ove - what Browser are you using? It must be Firefox or Chrome.

[Kevinkun]

what's the android version? is your Companion the latest version? Is any problem when compile to apk?

[Ove_Halseth]

Found a workaround in this thread:

Java Error Error from Companion: java.lang.RuntimeException: invalid syntax in eval form: :8:1: caught exception in inliner for # - java.lang.RuntimeException: no such class:

Is this for PC?

It's apparently a bug, and the workaround is to load your app in AI Companion first. After that Emulator will work for that session.

[ChrisWard]

That is not a 100% solution since the Emulator is not compatible with everything you throw at it.

If you have the AI2 Companion on a device for testing, it is better to use it rather than the Emulator - you are then testing how Android executes your code and how Android displays your GUI.

[mistik1]

Guys this is a bug.
I've tried with the simplest app, just a button or something like that add any extension at all and Companion with not work period until you remove the extension.
Can one of the devs point me in a direction to look so I can go after the code that does this.

[gordonlu310]

@mistik1

I've tried with the simplest app, just a button or something like that add any extension at all and Companion with not work period until you remove the extension.

Are you using the CompCreator extension or another extension? Please point it out before you reply.

Also, please, still show your blocks and the extension version that you are using before jumping to a conclusion that "this is a bug". The extension you are using may be an older version that have some bugs, and your blocks may have something missing (such as initializing a view for some extensions).

How to ask a question (open new topic)

Before you ask a question / open a new topic please take care of the following points: The forum was previously searched for similar topics / issues. Give a precise (detailed) description of the issue / bug, the goal. Show the (relevant) blocks (images, screenshots of blocks in high quality). Debug your blocks (connect to Companion and right mouse click: → Do it). Name the Android / iOS version running on your (test) device. Do not open multiple threads on the same topic. If you haven't al…

[mistik1]

@gordonlu310 What part of ANY extension don't you understand.

[gordonlu310]

I'm sorry, I misread your post.

If you haven't, you should exit the companion and reconnect again for starters. The extension is considered like an asset file and sent to the companion when you are connecting, and maybe, the extension is not sent to your device.

If this still persists, then you may have to build the app in order to test.

How to avoid runtime errors with the companion app

1. After importing an extension, please restart the companion app.

2. If you like to use an extension on a different screen, in Screen1 additionally drag the extension into the working area.

While starting the companion app, all necessary assets and also the imported extensions of your project will be copied to your device. So in case the no such class error shows up, the extension code to run the extension is not available on your device. Without that code the companion app is not able to execute methods from the extension.

In case restarting the companion app does not work for you after trying several times, then as it looks like the only way for you to test you app will be after building it using the apk file.

Taken from App Inventor Extensions | Pura Vida Apps.

If that still is a problem, clear the assets of your companion and try.

How to delete all files from assets with Companion

Here is an app that can be used to remove all files from assets with Companion - regardless of the Android version of the test device. This is sometimes necessary so that it still works (properly), for example after an extension update. deleteAssetsCompanion.aia (800.7 KB) Credit to Sunny - @vknow360 for his FileTools extension! [grafik] Android 9: [grafik] After that, disconnect Companion, reload the browser and reconnect to Companion...

[Anke]

@mistik1

add any extension at all and Companion with not work period until you remove the extension

Android or iOS?
Error message? Post a screenshot of it.

[mistik1]

I am using Android ver 9 on my phone, connected via USB
The extension I am currently trying to use is ColinTreeListView but that same happens no matter which I try (FirebaseAuth, FirebaseStorage, TaifunTextBox and more always fails).
I will try that clear assets shortly.

[mistik1]

This is actually funny (not).
I imported that deleteAssetsCompanion.aia, certainly does not load into companion, so I built it and installed and list files show blank array delete files seems to do nothing.
I restart the browser and companion upon restart the deleteAssetsCompanion was the last project so it autoloads and wham case in point error.

[Anke]

Does this simple test app work for you (with TaifunTextbox extension):
TaifunTextbox.aia (18.8 KB)

If not, post a screenshot again and try to connect via "AI Companion" (WiFi).

[mistik1]

I got a different error now.

BTW: I saw another flash by before that

[Anke]

Build the APK and try ...

[Anke]

@mistik1

I got a different error now.

Did you connect via "AI Companion" (or via USB again)?

[mistik1]

Via USB, I have no WIFI to try.
For what its worth I've been filtering logcat and I see a bunch of _values POST but I don't see _extensions.
12-25 04:59:03.449 20200 20254 D AppInvHTTPD: POST '/_values'

[Anke]

So did you try testing with the APK?