Not reproducible

On Mac: UnityFbxSdkNative_2_0_0.bundle registered as malware

mrstruijk 8 months ago updated by Peter - Soxware Developer 7 months ago 3

Hi Peter, 

When I'm trying to export as FBX (binary, 2011) on my Mac, it yells at me that UnityFbxSdkNative_2_0_0.bundle is malware. It then really wants to move this file to the bin, and can not continue with the export. 

Using .anim export for now, which is fine, but just wanted to let you know. 

Best, 
Maarten 

UMotion Version:
1.21
Unity Version:
2019.3.7f1

Answer

Answer
Not reproducible

"However, on another project running UMotion 1.20p07 on Unity 2019.3.7f1 this issue did not occur, also not when I upgraded to 1.22 (still in 2019.3.7f1), and also not when I upgraded Unity to 2019.3.9f1."

Ok if it works in a different project then this doesn't sound like a general problem. Chances are high that something went wrong during installation (of UMotion). Maybe the *.bundle wasn't extracted correctly (or maybe multiple versions of UMotion in the same project).

Best regards,
Peter

GOOD, I'M SATISFIED
Satisfaction mark by mrstruijk 7 months ago
Under review

Hi Maarten,
thank you very much for reporting this issue.

That is really strange (and is a false positive of course). Is this message coming from an anti virus software or from the Mac OS directly? Have you had the *.FBX export working in the past? Does uninstalling and re-installing UMotion help?

Best regards,
Peter

Hi Peter, 

It is a message from MacOS directly, not from any antivirus. I don't remember if I had issues with the FBX exporter in the past on Mac, since I usually use UMotion on my Windows work PC. Reinstalling is not an option at this moment since I need to make sure the software I'm using keeps working, because deadlines and such.


However, on another project running UMotion 1.20p07 on Unity 2019.3.7f1 this issue did not occur, also not when I upgraded to 1.22 (still in 2019.3.7f1), and also not when I upgraded Unity to 2019.3.9f1. 

I hope this helps!

Maarten  

Answer
Not reproducible

"However, on another project running UMotion 1.20p07 on Unity 2019.3.7f1 this issue did not occur, also not when I upgraded to 1.22 (still in 2019.3.7f1), and also not when I upgraded Unity to 2019.3.9f1."

Ok if it works in a different project then this doesn't sound like a general problem. Chances are high that something went wrong during installation (of UMotion). Maybe the *.bundle wasn't extracted correctly (or maybe multiple versions of UMotion in the same project).

Best regards,
Peter