@Patel
Thanks for the link. I have now switched to the extension ClickEvent. Works in my app as well.
@Anke
Thank you very much for your efforts.
I test your extension regarding the error.
Which extension should I use? The version in the 1st post or the version created with Rush?
Frank
Additive:
The extension using Rush produces an error when dragging it into the mobile phone in the designer, see: error.txt (5.3 KB)
Your extension from the first post seems to work after the first tests. I keep testing...
After you have imported an extension, disconnect the companion by Connect > Reset connection. The companion should then automatically exit. If it doesn't, exit the companion and connect again.
That is because Frank imported the extension after he connects to the companion. When you scan the QR code to connect, the computer sends all extensions and assets to the companion, but it shouldn't send extensions during the connection.
Hmm...that's interesting. One of my found errors was resolved by restarting the companion because the user upgraded the extension but did not restart it.
I find this in Taifun's webpage:
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.
and:
After importing an extension, please restart the companion app.
Usually set and coerce property error occurs if you empty sockets/slots in your Screen1 blocks. Check warnings or errors in Screen1, fix them and try again
on first run of the app the file can't already exist in event Screen.Initialize
and if it exists, then it was not created by your app...
in this case you only can use SAF to read it...see again the overview by @Anke
