Unity - Firebase - Issue while making x86 (Intel) Builds

312 views
Skip to first unread message

Tejas Shah

unread,
Oct 5, 2018, 7:26:33 AM10/5/18
to Firebase Google Group
Has anyone faced any issue while making x86 (Intel) builds with Firebase on Unity? We've been facing issues recently with this and are unable to make the builds with x86. 

We've tried: 
- enabled the auto jar resolution.
- downgrade the firebase version to 4.5 from 5.2.1

The error is something like this:
Filename: ./artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
09-28 04:48:09.687 27220-27241/? E/Unity: DllNotFoundException: App
                                              at (wrapper managed-to-native) Firebase.AppUtilPINVOKE/SWIGExceptionHelper:SWIGRegisterExceptionCallbacks_AppUtil (Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate,Firebase.AppUtilPINVOKE/SWIGExceptionHelper/ExceptionDelegate)
                                            at Firebase.AppUtilPINVOKE+SWIGExceptionHelper..cctor () [0x00000] in <filename unknown>:0 
                                          Rethrow as TypeInitializationException: An exception was thrown by the type initializer for SWIGExcepti

Any help would be appreciated. 

Regards,
Tejas

Stewart Miles

unread,
Oct 5, 2018, 3:06:02 PM10/5/18
to Firebase Google Group
We don't ship x86 (32-bit) DLLs at the moment.  We only currently support 64-bit (x96_64) targets right now.  Also, just a reminder that our desktop support is meant for testing inside the Unity editor not shipping a finished product.

Cheers,
Stewart

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/b0f8b0c5-eff1-40b9-b574-dd49f5c94139%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tejas Shah

unread,
Oct 8, 2018, 8:53:17 AM10/8/18
to Firebase Google Group
Hi Stewart,

Thank you for the response. However, we are trying this for Android builds (for x86 Android devices). 

Is there something else that we are supposed to do for x86 Android devices? 

Regards,
Tejas

Stewart Miles

unread,
Oct 8, 2018, 12:36:20 PM10/8/18
to Firebase Google Group
The Android Resolver will strip all architectures that are not in use from the AARs in Plugins/Android.  We ship AARs with native libraries (srcaar files under Firebase/m2repository) . for all architectures supported by Unity at the moment x86, armeabi-v7a and arm64 .

For example:
$ unzip -l Assets/Firebase/m2repository/com/google/firebase/firebase-app-unity/5.3.1/firebase-app-unity-5.3.1.srcaar
Archive:  Assets/Firebase/m2repository/com/google/firebase/firebase-app-unity/5.3.1/firebase-app-unity-5.3.1.srcaar
  Length      Date    Time    Name
---------  ---------- -----   ----
      343  10-05-2018 03:29   AndroidManifest.xml
        0  10-05-2018 03:19   R.txt
       22  10-05-2018 03:29   classes.jar
        0  10-05-2018 18:10   jni/
        0  10-05-2018 18:10   jni/arm64-v8a/
  3633008  10-05-2018 03:29   jni/arm64-v8a/libFirebaseCppApp-5.3.1.so
        0  10-05-2018 18:10   jni/armeabi-v7a/
  2819768  10-05-2018 03:34   jni/armeabi-v7a/libFirebaseCppApp-5.3.1.so
        0  10-05-2018 18:10   jni/x86/
  3378312  10-05-2018 03:19   jni/x86/libFirebaseCppApp-5.3.1.so
      923  10-05-2018 03:29   proguard.txt
---------                     -------
  9832376                     11 files

If you select x86 as one of the target architectures in Unity with auto-resolution enabled in the Android Resolver, you'll end up with the appropriate contents of the AAR processed and placed in Assets/Plugins/Android e.g...

$ find Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1 -type f
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/proguard.txt.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/AndroidManifest.xml
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/project.properties
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/R.txt.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs/x86.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs/classes.jar
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs/x86/libFirebaseCppApp-5.3.1.so.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs/x86/libFirebaseCppApp-5.3.1.so
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs/classes.jar.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/proguard.txt
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/R.txt
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/AndroidManifest.xml.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/libs.meta
Assets/Plugins/Android/com.google.firebase.firebase-app-unity-5.3.1/project.properties.meta

So it sounds like you may have auto-resolution disabled in the Android resolver when switching target architectures.

Cheers,
Stewart



Tejas Shah

unread,
Oct 8, 2018, 1:04:47 PM10/8/18
to Firebase Google Group
Thank you, Stewart. I'll ask the team to try this if they haven't already and come back with an update. 

Regards,
Tejas
Reply all
Reply to author
Forward
0 new messages