Out of nowhere, a problem with TaifunTools

[franz1 (Franz Balleis)]

Hello, maybe someone can help me. The DB_Open procedure suddenly throws this error.

Both versions throw the same bug.
regards Franz

[vknow360 (Sunny Gupta)]

Hi @franz1
You should use Is Companion property of Screen.

[Vaibhav]

There is no need to compare isDeveopment block with true/false

Just pass the isDevelopmemt block alone as the if parameter

[franz1 (Franz Balleis)]

Hi Vaibhav take a look at the 2nd screenshot. This was previously, as you suggest, but doing the same garbage

[Vaibhav]

Oh sorry I overlooked it!

[franz1 (Franz Balleis)]

Hi Sunny thanks for your tip. Will consider it in the future. But in my case, I think I crashed the online interpreter. Now the ImportDatabase is suspect. Can we somehow reset it?

[vknow360 (Sunny Gupta)]

@Taifun would like to answer your question.
Usually we get that error when we have error in any extension (when any method is removed) and try to use other methods of extension.
In Apk you will not get the error for other extensions.

[Taifun]

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.

Taifun