Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    mohammedmsadiq
    @mohammedmsadiq
    XL: Handshake connection timed out
    XL: Handshake server unreachable 10.0.3.2
    XL: =============== LiveXAML Important Information ===============
    XL: Failed to find find a handshake server
    1) Is phone connected to the same WiFi network?
    2) Are ports 53031 and 53032 opened in firewall?
    3) If On Windows, make sure that xlserver.exe is running
    XL: ==============================================================
    facing this issue on device and simulator
    this is on iOS
    Mihhail Maslakov
    @ionoy
    @mohammedmsadiq are you sure you have LiveXAML extension enabled?
    also, you could try using LiveSharp instead. it has LiveXAML integrated and supports the same license ( www.livesharp.net )
    Michelangelo
    @mfranc28
    Hi all, from a couple of days every time I started VS2019 Mac I see this message "Do you want to temporarily trust this certificate in order to connect to the server at www.livexaml.com"
    And after hit Yes, seems that LiveXaml don't work
    Mihhail Maslakov
    @ionoy
    @mfranc28 that must be something new in the VS for Mac
    can you try using LiveSharp https://github.com/OYIon/LiveSharp/releases/tag/v0.9.11
    it has LiveXAML integrated
    also, visit https://gitter.im/LiveSharp/Lobby for more info
    Transferr3
    @Transferr3
    Hey
    I have a question, is any1 here ?
    anyway solved :D
    Mihhail Maslakov
    @ionoy
    Good to know :)
    ZonderZout
    @ZonderZout
    Anyone here?
    I got the same error message as @RuidynyDev, whichj brought me here :)
    Mihhail Maslakov
    @ionoy
    hey @ZonderZout
    can you create a sample project?
    ZonderZout
    @ZonderZout
    I would, if I had the time =) I switched from LiveXaml to HotReload, then quickly deleted that crap again and I'm now running LiveSharp. Which... gives the same error. But only for the first page of the application (which might me a bit tricked out). Other pages do work nicely now
    I could send you the Xaml/Cs for the page that gives the error to check out
    Lyndon Hughey
    @LyndonHughey_twitter
    @ZonderZout You can't expect someone to take the time to isolate the millions of variables that exist in your project when you can't take the time to create a repo. Help code owners out by creating a quick sample. It will ensure they can spend their time fixing your problem rather than trying to create a project that may or may not reproduce your issue.
    ZonderZout
    @ZonderZout
    I meant to say that my immediate problem is "solved" (as in; does not occur on the pages I need to work on) and I lost time on trying to work around the problem. I'll happily fix a repo when I am caught up, but until then; sometimes a quick scan of some Xaml might be enough to identify a problem.
    But no worries,
    Mihhail Maslakov
    @ionoy
    @ZonderZout I tried to recreate this issue when @RuidynyDev posted it and couldn't
    That's why it would be better if you could send me something that I could run myself
    Anyway, please tell me if it happens again on a more important page
    Mark Zhukovsky
    @mzhukovs
    @ionoy hey Mihhail, we had exchanged a few emails on this (I am the one with the issue of LiveXAML showing both "trial expired" AND "active license detected" at the same time, and getting the "cannot connect" error when clicking Activate)
    I got this in the Application log from windows Event Viewer:
    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentException
    at XamarinLive.VisualStudio.LicenseInfo..ctor(System.String, System.String)
    at XamarinLive.VisualStudio.Activation.LoadLicenseInfo()
    at XamarinLive.VisualStudio.XamarinLivePackage.ShowWindow(System.Object, System.EventArgs)
    at System.Windows.Threading.DispatcherTimer.FireTick(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    it's actually causing my VS to crash a lot upon loading
    any ideas?
    Mark Zhukovsky
    @mzhukovs
    P.S. I can confirm that I tried the vsix you sent me, I completely uninstalled the existing extension first, then installed the one you sent, and result is the same.
    Mark Zhukovsky
    @mzhukovs
    Update
    I have switched to LiveSharp and was able to load LiveXAML license there and it works perfectly, and is AWESOME... very nice work (love the separate inspector and other things in the UI as well). Don't think there's any looking back at this point so can probably just disregard this bizarre issue.
    Mark Zhukovsky
    @mzhukovs
    but to confirm - LiveXAML functionality will continue to work via LiveSharp since I was able to load the license there, even after LiveSharp trial expires?
    Also - no lifetime license option for LiveSharp?
    Mihhail Maslakov
    @ionoy
    @mzhukovs I'm glad it works with LiveSharp! Your LiveXAML will continue working with LiveSharp for updating the XAML, no problem. As for C# updates, the monthly LiveXAML license will work as-is, but the permanent license will expire in a year or two. I know it kinda sucks, but I don't plan on permanent licenses for LiveSharp at this point. It's a MUCH more complicated product compared to LiveXAML and it basically takes all of my time. I don't suppose the workload situation will improve it the near future, hence the lack of a lifetime license...
    thanks for posting the stacktrace, I will look into it
    are you working on a VM?
    Mark Zhukovsky
    @mzhukovs
    yes
    Virtual Machine
    work issued
    Mihhail Maslakov
    @ionoy
    I think that's the problem... LiveXAML licensing engine uses PC ID for activation
    Mark Zhukovsky
    @mzhukovs
    welp, that's that
    guess LiveSharp has diff mechanism as it seemed to work there without issue
    mariajoserabaza
    @mariajoserabaza
    Hello everyone! We are trying to release an app. We decided to remove LiveXaml package from it to decrease the app size but the app is crashing. Any idea of why is this happening?
    Mihhail Maslakov
    @ionoy
    hello @mariajoserabaza
    as long as LiveXAML NuGet package is removed from the project, it doesn't have any influence on the runtime
    mariajoserabaza
    @mariajoserabaza
    okay, thank you!