Ok, not sure what I did, but telneting to ports 12124 and 12122 works now:
telnet 10.0.0.35 12124
Trying 10.0.0.35...
Connected to 10.0.0.35.
Escape character is '^]'.
telnet 127.0.0.1 12122
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Event
149
{"Name":"Welcome","Data":{"Message":"You have successfully connected to the Fuse Daemon. You can find API docs on our webpage."},"SubscriptionId":-1}
Fuse is still not connecting, even though I try both IP’s.
But, look at the difference:
telnet 10.0.0.35 12122
Trying 10.0.0.35...
telnet: connect to address 10.0.0.35: Connection refused
telnet: Unable to connect to remote host
telnet 10.0.0.35 12124
Trying 10.0.0.35...
Connected to 10.0.0.35.
Escape character is '^]'.
telnet 127.0.0.1 12122
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Event
149
{"Name":"Welcome","Data":{"Message":"You have successfully connected to the Fuse Daemon. You can find API docs on our webpage."},"SubscriptionId":-1}
telnet 127.0.0.1 12124
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Only connecting to 127.0.0.1 gives an actual response on port 12122.
Connecting to 10.0.0.35 (WiFi IP) on 12124 just connects (no response).
Update: Re-installed fuse, still the same.
Just to clarify the 12122 vs. 12124 thing: Those are two different processes. 12122 is the Fuse daemon, which should only talk to the various Fuse processes on your local computer. This is for instance where the editor plugins connect to get code completion, build logs etc.
12124 is the port where preview processes connect (“the proxy”), to set up a connection to the correct Fuse project and get live updates for that project.
So it’s only the proxy on 12124 that needs to listen on the public IP.
The proxy on 12124 is not supposed to give a reply until you start talking to it, whereas the daemon on 12122 gives a welcome message.
To conclude: Everything seems fine with your telnet experiments. Would it be possible for you to try iOS preview on a physical device and see if that is working? Also, do you have an Android device available that you could try preview on?
Hey, was on vacation with spotty internet.
I’ll do some more tests today, if it doesnt work i’m reinstalling my Mac from scratch.
Hi,
I’m new to fuse. Unfortunately, this kind of error also run to me.
telnet 127.0.0.1 12122
telnet 127.0.0.1 12124
both are working fine.
how to solve this issue?
Thanks,
Aha, so it’s not just me!
You give me hope 
Fuse team, your turn, seems like it’s not isolated. I can be contacted via Skype if you like to dig in deeper.
Yes, I also can give more detail on this.
Fuse is really interesting.
Chandara and R0b0tn1k,
It would be very helpful if you could check whether this problem only happens in the iOS simulator, or if it also happens on a real device (iOS or Android).
It is also happen on real device and simulator but run in Fuse Studio is ok …
My device: iphone7
Development: macOS Sierra
Trying Android:
blabla:vinyl-store bla$ fuse preview -t=Android
Fuse 1.1.1 (build 13893)
Configuring (3.6 s)
Compiling syntax tree (2.4 s)
Generating code and data (12.9 s)
Building Android app
2/2: VinylStore.apk
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
And it just stops.
I can see the device on ADB:
./adb devices -l
List of devices attached
55c3cae87ce4 device usb:336592896X product:markw model:Redmi_4 device:markw
Am I doing something wrong?
UPDATE:
No, wait it did launch, BUT this happened:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
(2:50)
Build completed in 189.08 seconds
Installing APK on 1 device(s)
Launching activity 'VinylStore'
ERROR: Too many open files. (pass --trace for stack trace)
fuse: Android run failed
Ok, switched devices, it finally installed.
However, the error is “Fuse not running”. Tried changing IP’s manually typing it in, to no avail.
R0b0tn1k:
“Fuse not running” is actually progress! “Failed to connect” means the app can’t connect to Fuse at all. “Fuse not running” means it managed to connect to the computer (the proxy on 12124), but that the project for that app is not opened in Fuse. When you got that message, are you sure you had the project open in Fuse?
Chandara:
Which exact error message are you getting? “Fuse not running” or “Failed to connect”?
I had the project open in Sublime. Should I have the preview running in Fuse as well?
Yes, the project has to be open in Fuse itself when you preview on a device.
Ok, let’s test that theory…
Seems to be running!
So, what have we learned:
- Fuse local preview has to be running with the app loaded
- Be on the same WiFi (was already)
- Run fuse preview -t=iOS to get iOS preview as well
I seem to remember from the videos that one preview made all other previews (iOS and Android) sync.
How do you do that?
Seems to be running!
Glad to hear it’s finally working!
So, what have we learned: 1. Fuse local preview has to be running with the app loaded 2. Be on the same WiFi (was already) 3. Run fuse preview -t=iOS to get iOS preview as well
Correct. For point 3, you can launch it from the menu in Fuse as well, if you don’t prefer the command line.
I seem to remember from the videos that one preview made all other previews (iOS and Android) sync. How do you do that?
What do you mean by “sync” here? If you make a change in Fuse Studio or an editor, those changes are instantly reflected across all previews.
Hi All,
It seems working.
I need to run Fuse Studio during the preview, I use Visual Studio Code.
I test another scenario to deploy to a real device. it is also working.
However, this behavior is not seem making sense at all.
Why do we need to run Fuse Studio during the preview and deploy?
Thanks,
Fuse only needs to be running during preview. If you export your app, it will work normally without Fuse running.
The reason for requiring the project to be open in Fuse when you’re previewing your app, is for Fuse to be able to watch the project files on disk, react to changes and update the preview(s) running on your device(s). In addition, you get the benefits of having the log view and error view available for your project.
Hi Guys, I’m facing the same problem.
My environment is Fuse 1.2.1, Mac OS Sierra 10.12.6.
On both, iOS (device and simulator) and Android, with Local Preview running.
