Syncplay doesn't launch

[Kehanort]

I just installed Syncplay 1.6.8 and it refuses to launch with the error?

Errors in 'Syncplay.exe' - See the log file 'C:\Program Files (x86)\Syncplay\Syncplay.log` for details

All the log shows is this:
PySide2/init.py: Unable to import shiboken2 from C:\Program Files (x86)\Syncplay\lib/libsync.zip

I've already updated Microsoft Visual C++ 2015 Redistributable both x86 and x64 and still nothing seems to work.

[abhiraj2]

having the same issue on one of my laptops, but weirdly not on two others

[abhiraj2]

It appears that the issue only exists on the latest release, I just checked 1.6.7 and it works just fine.
It might have something to do with the weird path " C:\Program Files (x86)\Syncplay\lib/libsync.zip" since it uses twp different types of connectors "/" and "\"

[Et0h]

If it works on some laptops and not others then I don't think the direction of the slashes is the issue. I think that might just be shorthand for it saying "it isn't working". It is interesting that it works on some laptops and not others, it might depend on whether certain common dependencies are installed on the devices.

Does installing the latest version of the .NET Framework 4.8 fix the issue? https://dotnet.microsoft.com/download/dotnet-framework

It is very helpful to know that it works fine with Syncplay 1.6.7. Does the issue occur with both the installed and portable versions of Syncplay 1.6.8?

[Et0h]

Okay, I've created two different builds from my own machine. Please test them and let me know if they work:

• https://github.com/Et0h/syncplay/releases/download/168test/Syncplay-168-Test1.zip
• https://github.com/Et0h/syncplay/releases/download/168test/Syncplay-168-Test2.zip

[samurai-legend]

Test-1 worked for my friend thanks a lot :D cheers

[Et0h]

Those who have had a problem (or whose friends had a problem): Was this using the 32-bit (x86) or the 64-bit (x64) version of Windows 10?

[spidermatt99]

I have the problem on 64-bit Windows 10, with both the portable version and installed. The test zips don't work for me. Nothing happens when trying to launch the exe, not even an error message.

[Et0h]

@spidermatt99 And did Syncplay 1.6.7 work fine for you? When it comes to debugging, the more information the better.

[abhiraj2]

Both the test versions worked just fine on the laptop that wasn't able to run the official latest release but was able to run 1.6.7

[spidermatt99]

@spidermatt99 And did Syncplay 1.6.7 work fine for you? When it comes to debugging, the more information the better.

Yes, 1.6.7 continues to work fine.

[Harry466]

Okay, I've created two different builds from my own machine. Please test them and let me know if they work:

• https://github.com/Et0h/syncplay/releases/download/168test/Syncplay-168-Test1.zip
• https://github.com/Et0h/syncplay/releases/download/168test/Syncplay-168-Test2.zip

Thank you so much. your 1st test file worked for me:)

[albertosottile]

So, it seems the issue is caused by either Python 3.8 or PySide2 5.15, as these are the differences between the Test1 build and 1.6.8 release (the Test1 build embeds Python 3.6 and PySide2 5.12).

Since the issue is caused by dependencies, I am not sure how we should approach this. For the moment, I would encourage all the people that experience this issue to try again with the Test1 build and confirm this fixed the bug for them.