Closed ylluminate closed 3 years ago
amouro
commented
5 years ago I rebuild the app with the latest Xcode 10 on Mojave, and it works great between High Sierra and Mojave. The last commit by @abyssoft is working, and hopefully they release a new build for users.
Grunerd
commented
5 years ago Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build.
I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far.
(Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
ylluminate
commented
5 years ago One thing I found too was that I had to disable and then re-enable (uncheck and then check again) the setting within System Preferences > Security & Privacy > Accessibility > teleport.app.
You know, one other thing that I found that seems crazy is that teleport seems somehow "faster" in 10.14 than it did in 10.13... Screen switching happens a little faster and things seem in some way smoother so far.
adhamattia
commented
5 years ago One thing I found too was that I had to disable and then re-enable (uncheck and then check again) the setting within
System Preferences > Security & Privacy > Accessibility > teleport.app.You know, one other thing that I found that seems crazy is that
teleportseems somehow "faster" in 10.14 than it did in 10.13... Screen switching happens a little faster and things seem in some way smoother so far.
Works with me thanks 👍
chromixsea
commented
5 years ago On Sep 27, 2018, at 1:33 AM, Adham Attia notifications@github.com wrote:
One thing I found too was that I had to disable and then re-enable (uncheck and then check again) the setting within System Preferences > Security & Privacy > Accessibility > teleport.app.
You know, one other thing that I found that seems crazy is that teleport seems somehow "faster" in 10.14 than it did in 10.13... Screen switching happens a little faster and things seem in some way smoother so far.
Works with me thanks 👍
I'm still having the problem I had before which is that I can connect from my High Sierra machine to my desktop Sierra machine but not the other way around - which is the direction I need
any possible hints on that?
thanks
Grunerd
commented
5 years ago On Sep 27, 2018, at 1:33 AM, Adham Attia @.**> wrote: One thing I found too was that I had to disable and then re-enable (uncheck and then check again) the setting within System Preferences > Security & Privacy > Accessibility > teleport.app. You know, one other thing that I found that seems crazy is that teleport seems somehow "faster" in 10.14 than it did in 10.13... Screen switching happens a little faster and things seem in some way smoother so far. Works with me thanks 👍 I'm still having the problem I had before which is that I can connect from my High Sierra machine to my desktop Sierra machine but not* the other way around - which is the direction I need any possible hints on that? thanks
I had that issue once and the way to go was to wipe all config files and start fresh - make sure both machines have a certificate and go the encrypted route. Without encryption, it would fail on one of my machines all the time. And make sure that you get the "accept connection" popup and accept it properly. Automatically accept also didn't work for me in that specific situation. Never had that on High Sierra <-> High Sierra or High Sierra <-> Mojave so far.
tchek
commented
5 years ago Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build.
I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far.
(Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
Thanks ! It work nice on Mojave 10.14 (18A391)
tchek
commented
5 years ago I spoke a little fast, it works, but it must be reconfigured after each machines reboot, and it's not easy...
tatatajp
commented
5 years ago Thank you for the build. It works well between Macs on Mojave. Before Mojave, it worked on High Sierra<->Snow Leopard(Teleport 1.1.3). I will be happy if revised build becomes to accept connection to old Macs in future.
hubeluk
commented
5 years ago I'm using it on Mojave controlling a Mac on High Sierra and its been rock solid. The only issue I have is a small vertical white line on the side of the screen on Mojave. Its only noticeable on a dark background but hopefully it won't burn into the screen
tchek
commented
5 years ago Same here with the thin vertical white line on the side of the screen on Mojave, in addition to having to reconfigure it after each reboot !
trendmicrojohn
commented
5 years ago Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build.
I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far.
(Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
Hey... nice job Thank you !!! it works on Mojave!
johanhenselmans
commented
5 years ago Turns out the XCode10 conversion does not work because of one value: Under Apple Clang - Code Generation The Value "No Common Blocks" is converted to "Yes". the default value is "No". Resetting this value to No makes it build properly.
espresso1736
commented
5 years ago This worked for me for a while after upgrading one Mac to Mojave, and then it stopped working when I rebooted the other Mac, which is running High Sierra. Re-installed 1.2.2 on both Mac's, and now I can share the mouse & keyboard from the High Sierra Mac to the Mojave Mac ... but not the other way around, that that's what I need. Any thoughts on how to fix this would be most appreciated - I've come to rely on teleport and really miss it. Thanks.
francosolerio
commented
5 years ago A quick and dirty fix for the white line on the side of the screen is setting _transparentColor to nil in the initialize method of TPHotBorderView:
+ (void)initialize
{
if(self == [TPHotBorderView class]) {
_highlightColor = [NSColor redColor];
_visibleColor = [NSColor blueColor];
_transparentColor = nil;
}
}
@francosolerio
I'm not a developer please be kind to explain where and how do you put these lines?
tomads
commented
5 years ago @francosolerio
Thx, works here. The white border is now black ....
trendmicrojohn
commented
5 years ago for up dude y p u p
On Sun, Nov 18, 2018, 11:44 AM tomads <notifications@github.com wrote:
@francosolerio https://github.com/francosolerio
Thx, works here. The white border is now black ....
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/abyssoft/teleport/issues/42#issuecomment-439719868, or mute the thread https://github.com/notifications/unsubscribe-auth/AqWmmezOCjPZatAEgkXGncFa6KVjSVclks5uwbijgaJpZM4WCUqG .
DrakeSeven
commented
5 years ago Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build. I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far. (Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
Thanks ! It work nice on Mojave 10.14 (18A391)
Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build.
I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far.
(Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
Works great on Mojave 10.14.1! I share mouse and keyboard between: Teleport 1.2.1 on High Sierre 10.13.6 (MacBookPro 17") <-> Teleport 1.2.2 on Mojave 10.14.1 (MacBookPro 15")
hubeluk
commented
5 years ago Be nice is someone could link to a build that gets rid of the white line.
Grunerd
commented
5 years ago Be nice is someone could link to a build that gets rid of the white line.
Your request is my demand.
Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1
hubeluk
commented
5 years ago Be nice is someone could link to a build that gets rid of the white line.
Your request is my demand.
Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1
Thanks very much!!! Works like a charm
QbMoto
commented
5 years ago Yes, building teleport 1.2.2 works. For now, here's the build I made. No changes to the code whatsoever. If you open the project in Xcode, you need to resist the urge to follow the recommendations Xcode offers - that will break the build.
I use it on 10.13.6 and 10.14.0 and they work pretty solid, so far.
(Potentially unstable, use at your own risk. All copyright etc by @abyssoft - I just hit the build-button) teleport_1.2.2.zip
Thank you for the share!!!!!
speedmax
commented
5 years ago Thanks for the build
adhamattia
commented
5 years ago Be nice is someone could link to a build that gets rid of the white line.
Your request is my demand.
Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1
Man, YOU ARE A HERO I have gave up and went and purchased this similar app ShareMouse and it is total crap compared to teleport YOU SAVED US Please find a way to release this fix somehow and make it knows, cause not everyone will be checking the issues and comments Great Job Thanks
ylluminate
commented
5 years ago Perhaps someone should set up a donation option here. This is fantastic to keep having updates even in this maintenance mode.
iknowzo
commented
5 years ago My productivity the past few months practically diminished after I lost compatibility when I updated to Mojave. MAJOR THANK YOU for the release!
ylluminate
commented
5 years ago @Grunerd you don't happen to know how to modify Teleport to work with dark mode do you? For example, when configuring the options it's impossible to read unless you switch back to light:
ggowing
commented
5 years ago Thank you for helping get this working! This was my big obstacle in using the new 2018 Mac mini as Synergy and ShareMouse do not do gestures. Awesome.
ylluminate
commented
5 years ago Unfortunately I'm hitting some walls here again in Mojave it would seem. I changed hardware around (swapped drives into another system) and now I'm getting:
I guess the real problem is that Configure -> Settings doesn't really function properly anymore. For example, if you "Show trusted hosts..." you can view them, but "backspace" (delete) doesn't remove them. It seems like the encryption and general connection workflow within the app are broken.
UPDATE: I hit a little luck here. I was able to remove SOME preferences (I must be missing some somewhere because all settings are not reset to vanilla when I do this...):
# FIRST KILL teleport!
rm ~/Library/Preferences/com.abyssoft.teleport.plist*
rm -fr ~/Library/Caches/com.abyssoft.teleport
rm -fr /private/var/folders/cb/<PUT_YOUR_PATH_HERE>/C/com.abyssoft.teleportAnd then when I started it back up it did ask me for my keychain password and thus allowed me to start connecting again... But something is definitely a little strange here with encryption settings and a user's ability to control these.
horacebork
commented
5 years ago Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1 teleport-1.2.2-build2.zip
i have been using teleport for ages and love it. it has been a great app for me.
just upgraded to Mohave 10.14.5 and teleport stopped working. i have tried several versions of teleport, then found this thread. this build (ylluminate's teleport-1.2.2-build2.zip) is close but still not fully functional (for me). and i have rebooted as suggested by ylluminate.
it has gotten me much closer to the goal of functioning teleport on mojave than any other version i have tried.
what i can do: 1) start the app and go the config dialog box 2) see other computers on the network and position them around my mojave screen 3) see the "red line" shift as i position other computers around the screen
what i cannot do: 1) actually move the mouse over to the other computers
in the screen shot, "magneto" is mojave 10.14.5, bucky is 10.6.8 snow leopard, graviton is high sierra 10.13.6. why magneto is there twice is a mystery.
when magneto was high sierra 10.13.6, all worked perfectly between the three.
any help would be greatly appreciated.
emailkono
commented
5 years ago Worked great! Able to control Mojave on 2013 iMac and Yosemite on 2009 iMac. I agree it seems to work better and faster after installing the teleport-1.2.2-build2.zip file.
Needed no other tweaks.
Thanks!
jordangoody
commented
5 years ago Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1 teleport-1.2.2-build2.zip
i have been using teleport for ages and love it. it has been a great app for me.
just upgraded to Mohave 10.14.5 and teleport stopped working. i have tried several versions of teleport, then found this thread. this build (ylluminate's teleport-1.2.2-build2.zip) is close but still not fully functional (for me). and i have rebooted as suggested by ylluminate.
it has gotten me much closer to the goal of functioning teleport on mojave than any other version i have tried.
what i can do:
- start the app and go the config dialog box
- see other computers on the network and position them around my mojave screen
- see the "red line" shift as i position other computers around the screen
what i cannot do:
- actually move the mouse over to the other computers
in the screen shot, "magneto" is mojave 10.14.5, bucky is 10.6.8 snow leopard, graviton is high sierra 10.13.6. why magneto is there twice is a mystery.
when magneto was high sierra 10.13.6, all worked perfectly between the three.
any help would be greatly appreciated.
same issue here too. running a 2010 iMac with high Sierra, and having trouble getting it to control a MacBook 12 2017 with Mojave. seems sometimes if I delete the prefs and caches it works for a while, but if I restart the MacBook, it for sure breaks it.
any ideas?
Grunerd
commented
5 years ago Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1 teleport-1.2.2-build2.zip
i have been using teleport for ages and love it. it has been a great app for me. just upgraded to Mohave 10.14.5 and teleport stopped working. i have tried several versions of teleport, then found this thread. this build (ylluminate's teleport-1.2.2-build2.zip) is close but still not fully functional (for me). and i have rebooted as suggested by ylluminate. it has gotten me much closer to the goal of functioning teleport on mojave than any other version i have tried. what i can do:
- start the app and go the config dialog box
- see other computers on the network and position them around my mojave screen
- see the "red line" shift as i position other computers around the screen
what i cannot do:
- actually move the mouse over to the other computers
in the screen shot, "magneto" is mojave 10.14.5, bucky is 10.6.8 snow leopard, graviton is high sierra 10.13.6. why magneto is there twice is a mystery. when magneto was high sierra 10.13.6, all worked perfectly between the three. any help would be greatly appreciated.
same issue here too. running a 2010 iMac with high Sierra, and having trouble getting it to control a MacBook 12 2017 with Mojave. seems sometimes if I delete the prefs and caches it works for a while, but if I restart the MacBook, it for sure breaks it.
any ideas?
Close teleport. Make a backup of ~/Library/Preferences/com.abyssoft.teleport.plist (~ equals /Users/
To make things easier when setting up teleport from scratch, set it to automatically accept connections.
jordangoody
commented
4 years ago hey guys, I just want to say teleport is amazing and there's nothing out there with multi-touch support so I really appreciate it.
anyway, I use it to control my MacBook from my iMac. both are running Mojave. I'm having an issue where if the computers go on different networks, like if I leave the house with my laptop, I can't get teleport working again until I run the commands and restart the iMac. I don't use encryption.
specifically, the iMac shows that the MacBook is connected and I see the flashing red to indicate where it is on the monitor, but the mouse just won't move over there until I reboot.
so.. rm ~/Library/Preferences/com.abyssoft.teleport.plist* rm -fr ~/Library/Caches/com.abyssoft.teleport rm -fr /private/var/folders/lt/jf9fs0h167b51h41tg8_9ktm0000gn/C/com.abyssoft.teleport then restart any idea how to avoid all that?
jordangoody
commented
4 years ago ... and now I cant get it to work at all from iMac to MacBook anymore. :( works fine from MacBook to iMac though! go figure! iMac sees the MacBook and lets me place it, but won't show me the contextual menu for it, or control it. any help would be much appreciated. this thing is awesome when it works.
Grunerd
commented
4 years ago Can you check if your MacBook gets the same IP address every time it connects to your home network? Teleport seems to have issues with hostnames that are not tied to a specific IP address.
You might also give the Control Request option "automatically accept" a try on your MacBook. I couldn't replicate when exactly, but sometimes the window that asks for requests on a first time setup wouldn't show up so I ran into the same issue as you described - red indicator on the border, but not actually being able to establish a connection.
jordangoody
commented
4 years ago Hey, yes, same IP.. it seems to be something with the master teleport, like, it shows the red line where the screen will be when I drag the tile in settings, but doesn’t flash when I set it, and then I can’t click on the options for the tile in settings either. Toggling share on the slave computer shows and hides the tile appropriately, so it sees it, but it’s not connecting.
Aside from the prefs and caches, where else does the mac keep record of teleport stuff? I see it still in the accessibility allowed apps list in privacy prefs, even after a complete uninstall and reboot. Should I try removing it some other way?
jordangoody
commented
4 years ago Suddenly it's working again, for now. this is like my 10th reboot. I really don't know what I did differently, maybe instead of removing teleport from the accessibility list, I re-selected it after replacing the app? could have sworn I did that before though... I'll keep looking; I realize my reporting isn't very helpful in narrowing this down.
jordangoody
commented
4 years ago had to move the laptop and its back to not working. when I reconnected to the network, I saw the red flashing on the side of the imac monitor so I thought we were good, but it wouldn't move the mouse over there.
I rebooted, same problem.
I deleted the prefs and cache, now in settings, I can see the MacBook and drag it to the side of the iMac tile, but it won't show me options, and when I close and reopen teleport, it doesn't remember I've dragged it so it just shows as available.
I also deleted teleport from the accessibility panel and rebooted. no dice. I'll keep trying.
jordangoody
commented
4 years ago hey idk if this is unorthodox or what, but can I offer a bounty for an updated version that works with mojave/catalina? I'd HAPPILY PayPal anybody who can fix this.. lets say $100? also, honestly, im not a dev, but im a product guy who believes in this thing, and if there's a dev out there who can help package this app for the App Store, I'd be down to help with marketing and provide some up-front advertising spend in exchange for a portion of the revenue. I think with sidecar coming out, there'll be a renewed market for virtual KVMs, and when it was working right, teleport was for sure the one to beat.
jordangoody
commented
4 years ago $200? does anyone on this thread feel up to match it? I can't be the only one who wants multi-gesture support in a virtual KVM. its so close!
Grunerd
commented
4 years ago I'd love to dive knee-deep into this app full-time, but right at this moment I simply can't afford doing that, even though it would be an absolute passion project.
To get your issue resolved, we need to make sure that your setup is "clean" and that we can gather information needed. I did some tests over here in my home network with multiple machines and macOS versions and I got it running flawlessly every single time by doing these steps.
Make sure you have a TimeMachine Backup of all your machines.
Delete ~/Library/Preferences/com.abyssoft.teleport.plist on every machine.
Delete ~/Library/Caches/com.abyssoft.teleport on every machine.
If possible, check /private/var/folders for anything com.abyssoft.teleport related and delete that on every machine as well
Make sure that teleport is properly listed in System Preferences -> Security & Privacy -> Accessibility on every machine. If in doubt, remove it and add it again. Doesn't hurt.
Make sure that teleport is listed in System Preferences -> Users ->
Make sure that the machines you want to connect "to" have Encryption enabled (create a new random certificate if necessary) and that they are set to "Automatically accept" - if you want to kvm in all possible directions, make sure that encryption is set up on all machines.
Do one full restart before starting to set things up for the first time. (Related to the encryption certificates)
Start setting your your teleport instances one Mac at a time. If you drag a desktop into position and it doesn't show immediately the "option" button underneath it, close teleport on the machine you are setting up as well as the machine that you tried to drag in position. Open it up first on the machine you tried to drag. Then the machine you tried to set up.
Once everything is set up, do some hardcore testing. Going into standby and out. Turning off Wifi and On. Rebooting. And make notes where there are hickups. And in what situation.
To give us a bit more information on this topic, please check the following
On your laptop, open Terminal (or iTerm if applicable) and just type in:
hostname
and press enter / return.
It will show the current hostname of your laptop within the domain of your home network. (For example, if you happen to be connected and managed via a fritzbox like I do, it's "laptopname.fritz.box".
Also check the "Trusted Hosts" list on the machine that you are trying to connect to and verify that this IP address is shown "somewhere" when you enter the following into your terminal:
ifconfig
That will show you the current network adapter configuration. (In my example screenshot, I entered ifconfig en0 because I know I only use the wifi connection and on my machine, that's the device 'en0')
One thing that's possible is that your hostname of your laptop is being changed because a similar hostname is on your work network already. For example, if there are two machines called "JordansMacBook" on the network - or if you happen to connect to the same network with the same machine via Wifi AND Ethernet at the same time (= two different MAC addresses, two different IP addresses trying to access via the same hostname - one internally gets renamed to JordansMacBook-2 and that's what macOS carries around until the next reboot). We had issues like that a ton on our university campus network which made debugging network applications based on hostnames outrageous - because it also happened when you moved a running laptop too quickly from one access point to the next - on one the laptop is still connected, the same doesn't notice it's the same machine and just forces you to receive a new hostname... There's also a chance that your laptop is attached to a different domain and that mismatches with the verification procedure in the current version of teleport. The domain isn't shown in trusted hosts, but if I remember correctly, it's also saved.
If we can identify what exactly is causing Teleport to go haywire here, we can figure out a way to work around that.
jordangoody
commented
4 years ago thank you SO MUCH for this! ok... i'm sorry to report that i'm currently stuck on step 9. no options showing up for the MacBook, and of course it isn't working... I re-did steps 1-8, but I'm hitting a wall.
one interesting thing is that first round of deleting the prefs, cache, and var files on the MacBook, and then restarting, I still saw the iMac listed as a trusted host, but then after the second round of deletes the trusted hosts is blank. ¯_(ツ)_/¯
anyway, both hostnames are showing without a -2, and here's the ifconfigs. again, I really appreciate you looking into this for me.
also, MacBook to iMac is working right now! just tried it... shame I need it the other way.. but I'll keep it running for now just to see how reliable it is.
oh and last thing- im using a Comcast router right now.. the new one, xb6 or whatever for gigabit, but im switching to eeros tomorrow. I'll let you know if that makes any difference.
thanks again, -j
jordangoody
commented
4 years ago UPDATE: I changed the service order on the network ports on the iMac, and suddenly teleport is working! I'll try rebooting a couple times, and keep you posted if it stops again.
Grunerd
commented
4 years ago UPDATE: I changed the service order on the network ports on the iMac, and suddenly teleport is working! I'll try rebooting a couple times, and keep you posted if it stops again.
So were you using the same Mac with MULTIPLE network connections to your home network at the same time? As in Cable + Wifi?
Oh and you can delete / edit out your "ifconfig" output above. It shows some hardcoded information (MAC addresses) regarding your Macs network ports. That stuff shouldn't be public - all I cared for was that YOU could verify yourself that the combination of hostname and ip address wouldn't change when rebooting / switching from your work wifi to your home wifi.
Glad that it seems to be working now. :)
jordangoody
commented
4 years ago (removed, thank you ;) )
I did have multiple connections for a bit, but then went back to just wifi. I had changed the service order just being lazy not wanting to unplug it.. actually it was over an airplay bug that's sorta similar in that if the computer was connected over ethernet, it would show the speakers but not play music.
anyway, the iMac stayed working through a reboot, but faulted again today when I set up my new eero network. same issue with the MacBook showing up but not letting me control it, so I switched the service order again, back to what it was yesterday (just putting ethernet at the top above wifi) and its working again.
now that I know the trick to kick it back online, this isn't so bad, and I'll see if/when it happens again. thanks!
style95
commented
4 years ago Hello folks. I am new to teleport. I installed the above manually-built binary on Mojave and it seems my mouse is working with a big delay on my submachine. It literally "teleports" around the screen.
Does anyone have any idea on this?
paullinford
commented
4 years ago I was trying to set this up. I had v 1.0.2 running under OSX 10.11.6 and wanted to prepare for inevitably needing to update to OSX 10.14.6 and came across this thread. How is the encryption certificate created, ie what settings are to be used? There are several options when Certificate Assistant opens.
jctim
commented
3 years ago @Grunerd thank you so much for the build, it works fine on Catalina!
Be nice is someone could link to a build that gets rid of the white line.
Your request is my demand.
Again: Use at your own risk. I had to reboot once after replacing the app for it to work with the certificate, due to a change in the signature. Still works like a charm for me on 10.13.6 and 10.14.1
When I attempt to run
teleporton Mojave (beta 7) I get a crash. I'm wondering if this is "as simple as" just rebuilding it with Xcode on Mojave?Here's the crash report: