Why could not connect to Homey (ws://172.17.0.1:30000)? - homey

I've created, validated and published my app by homey cli.
In 'Developer Tools', the app's state is 'Processing failed'.
When I try 'homey app run', got error as below:
hook#win10-pc05:/mnt/d/code/homey/com.alfred-iot$ homey app run
✓ Pre-processing app...
Added Driver `smart-lock`
✓ Validating app...
✓ Homey App validated successfully against level `debug`
✓ Creating session...
✓ Preparing Environment Variables...
— Homey.env (env.json)
— CLIENT_SECRET=Homey...D5ytl
— CLIENT_ID=D1f4L...tp04O
— WEBHOOK_ID=61c02...1ad57
— WEBHOOK_SECRET=6e06c...51ab5
✓ Started Local HTTP Server at http://0.0.0.0:30000
✓ Connecting to Homey...
✓ Connected to Homey
✓ Starting app...
✓ Started app
✓ Debugger running at 0.0.0.0:9229. Open `about://inspect` in Google Chrome and select the target.
✓ Starting `com.alfred-iot`, press CTRL+C to quit
Debugger listening on ws://0.0.0.0:9229/2af4135e-1fd0-402d-ac03-6a4cc889063f
For help, see: https://nodejs.org/en/docs/inspector
Could not connect to Homey (ws://172.17.0.1:30000).

You can click the red processing failed icon to see the error, it says that you are trying to publish your app for Homey Cloud but you are not a verified developer.
Are you setting "platforms": ["cloud"] in your app.json manifest? If so you should be able to publish your app after removing it.
Otherwise, could you share your app.json or a link to the source code of your app?

Related

Build error while running the native script application

Migrating my native script application to 8.1.5 version.
Fixed the errors that occurs when migrating the native script application.
Application build successfully in the emulator. After build successfully getting error in the application.
How to fix this issue?
Try this:
Go to AVD Manager, and click wipe data on the selected emulator:
Restart your machine (adb connection might be lost).
Then restart your project by running:
ns clear
ns run android
If that doesn't open the app on the emulator, run:
ns devices
Spot the emulator ID you want to run the app on
ns build android
ns deploy --device EMULATOR-ID
Note:
Make sure you've done all 4 blue steps in the cli message (in blue).

Flutter 1.22.0 IOS app connection lost issue

I have migrated to Flutter 1.22.0 from the older version. When I am trying to run the application in the IOS Simulator, it just opens the app and crashes and says connection lost. However in the Android Studio, it still shows it is running, I mean the Run & Debug button is disabled but the stop button is active.
The flutter run --verbose output is here.
Following logs I am seeing at the end after that nothing happens.
Launching lib/main.dart on iPhone 11 Pro in debug mode...
Running Xcode build...
Xcode build done. 18.4s
Configuring the default Firebase app...
6.26.0 - [Firebase/Core][I-COR000004] App with name __FIRAPP_DEFAULT does not exist.
6.26.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
[Firebase/Crashlytics] Version 4.1.1
Configured the default Firebase app __FIRAPP_DEFAULT.
6.26.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60600000 started
6.26.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled
6.26.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
Waiting for iPhone 11 Pro to report its views...
Debug service listening on ws://127.0.0.1:55184/qe2GMcl6YA3=/ws
Syncing files to device iPhone 11 Pro...
Lost connection to device.
Whenever I start the IOS simulator, it gives me the "Spotlight quit unexpectedly." error. See the below screenshot. Not sure whether it is related to this issue or not...
You are still using an older version of Flutter. v1.22.2 is released this week. Try to upgrade Flutter with flutter upgrade --force.

First Flutter App stuck at “Running Gradle task 'assembleDebug'… ” in Llnux Mint

I'm getting the following error while running my first flutter app in the terminal
Launching lib/main.dart on vivo 1802 in debug mode...
Running Gradle task 'assembleDebug'...
(This is taking an unexpectedly long time.)
I already tried downloading the gradle distribution separately and copy pasting it in my project's gradle wrapper and restarting android studio but it still doesn't resolve the issue.
I'm using Linux Mint 19.
Make sure you have an internet connection.When running an app for the first time, gradle needs to download some additional content
Check your connection to your virtual phone or your phone well. Make sure it doesn't disconnect while you are running the app
Before starting this building process, make sure:
USB debugging is enabled on your phone,
No app is currently running (and you are on your home screen),
While running your app for the first time on a phone, your phone will get a pop-up asking you to allow the installation of apps via USB.
Click 'allow' on it.
Not clicking 'allow' or simply ignoring it will make it seem like the build process is never-ending.

"Installation or uninstallation is not working temporarily" error when trying to launch Tizen watch application from Tizen SDK

When trying to launch the native watch application from Tizen IDE, I see the strange message "Certain application categories, such as "Watch Application", cannot be launched by "Run As".
Indeed, I try to use Run As from the project local menu to launch my app. But how else I am supposed to launch my application on the emulator?
The emulator device (watch) is up and running, visible on desktop as a separate widget. It is selected. The signing configuration is set up.
On the console output I see the message processing result : FATAL_ERROR [61].
I also tried to launch through the created launch configuration but this results the same error message.
The IDE logs show the following stack trace:
[2015.09.06 12:16:48][ERROR] ConnectionExplorer.java(658) - Fail to get platform log
[2015.09.06 12:18:59][ERROR] RdsDeployer.java(269) - Cannot partially upload or reinstall
org.eclipse.core.runtime.CoreException: [RDS] Cannot install application
at org.tizen.common.rds.RdsDeployer.newCoreException(RdsDeployer.java:699)
at org.tizen.common.rds.RdsDeployer.postInstall(RdsDeployer.java:634)
at org.tizen.common.rds.RdsDeployer.partialZipInstall(RdsDeployer.java:566)
at org.tizen.common.rds.RdsDeployer.deploy(RdsDeployer.java:267)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.deployApplication(TizenLaunchDelegate2.java:783)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.launchApplicationForRun(TizenLaunchDelegate2.java:504)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.launch(TizenLaunchDelegate2.java:216)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: org.tizen.common.sdb.command.message.CommandErrorException:
Error code: FATAL_ERROR
Error message:
Command: /usr/bin/pkgcmd -q -r -t tpk -n com.au.heywatch
Management: Installation or uninstallation is not working temporarily.
P.S. I add "eclipse" tag because Tizen SDK is very clearly Eclipse based IDE. Using Tizen IDE 2.3.1.
Watch face applications(Web/native) are never installed as widgets. You cannot see them in app menu.
Reason:
Within your tizen-manifest.xml file in your project, you'll find below line there
<watch-application appid="org.tizen.watchsample" exec="watchsample" ambient-support="true">
which makes your app as watch application and these apps are known as watch faces because they will be used in setting as the main watch in gear.
And on emulator, you cannot change the watch face on the home screen. Hence, you won't be able to test your watch application that way.
Had the same issue. My problem was certificate setup.
i followed there instructions: http://127.0.0.1:50224/help/topic/org.tizen.addon.certificate/html/dev_env/setting_author_certificate.htm
(link is from help and should work in browser when Tizen IDE is up, alternately you can go to Tizen IDE -> Help -> Help Content and search Certificate.
More specific: Distributor certificate i had was wrong (use the pass received by Samsung by email)
After fixing certificate, don't forget to right click your device in Connection Explorer and click Permit to install applications.

Blackberry Deployment Failed Error

I am new to Blackberry Development. Now while run the application on simulator I am getting an error like,
Deployment Failed: Info: Obtained qconn connection
Info: Begin device to host file sync
Info: All files already in sync
Info: File sync complete in 7ms
Info: Sending request: LAUNCH
Info: Action: Launch
Info: Debug native: on
Info: Launching com.shidhin.testDev_com_shidhin7fd6f305...
result::Invalid
Info: done
I had the same problem after deleting my target app in the simulator (without uninstalling it).
You can solve it like this:
1. Install BB10 / PlayBook App Manager as a chrome plugin. See details here.
2. Enter your simulator IP there (you can find it in the Device Manager, in momentics IDE).
3. Uninstall your app.
4. Then click run.
It should be working.