Origin of these 32-bit library files: libdouble-conversion, libxplat_perflogger_*

[VRsun2]

@Rob-Fireproof

Did you ever track down the source of those files? I’ve got the same issue. Not a huge deal - just causes a warning from the Oculus upload tools, but I’d like to know what they are.

No, unfortunately not. I didn’t have time to further investigate this.

[VinylPixels]

This is crazy! This thread is the only hit when searching for: libxplat_perflogger

Same as @Rob-Fireproof I got here because of Oculus / Meta build uploading. It keeps complaining about my build having libraries for both 64 and 32 bits, when I only have the armv64 selected in build settings. And while the “main” lib folder in the apk indeed only contains arm64-v8a, there is this armeabi-v7a folder inside /assets/lib/ which I guess triggers the warning…

Do we really not know where it comes from and how to stop it?

[IGuscin]

@VinylPixels

This is crazy! This thread is the only hit when searching for: libxplat_perflogger

Same as @Rob-Fireproof I got here because of Oculus / Meta build uploading. It keeps complaining about my build having libraries for both 64 and 32 bits, when I only have the armv64 selected in build settings. And while the “main” lib folder in the apk indeed only contains arm64-v8a, there is this armeabi-v7a folder inside /assets/lib/ which I guess triggers the warning…

Do we really not know where it comes from and how to stop it?

If you could share a repro project - we could try taking a look

[rgarand64]

Hi,
Still have this problem on 2022.3.62, have arm7 code in apk even if only arm 64 check.
don’t find any clue on this libxplat…
Anyone found comething ?
Robert

[mgear]

“complaining about my build having libraries for both 64 and 32 bits, when I only have the armv64 selected in build settings”

got this also in 6000.3.11f1 project for oculus quest app..

attached the packages manifest, if it could be one of those?
manifest.txt (1.8 KB)

*actually the .apk file does contain these