Jitsi-meet: Bitcode enable issue with latest code

Created on 14 May 2019  路  12Comments  路  Source: jitsi/jitsi-meet

Hi @saghul , I got issue while trying compile lastest code.

jitsi-meet/node_modules/react-native-webrtc/ios/WebRTC.framework/WebRTC' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target.

I have enabled Bitcode to true, but still no luck. Please help me out. Thanks so much

Most helpful comment

Run this script: https://github.com/jitsi/react-native-webrtc/blob/master/tools/downloadBitcode.sh It's part of the package, so you'll havee it in node_modules/react-native-webrtc/tools/downloadBitcode.sh

I need to re-think how to handle bitcode a bit better, maybe by integrating this script or something. I'll keep this open.

All 12 comments

Run this script: https://github.com/jitsi/react-native-webrtc/blob/master/tools/downloadBitcode.sh It's part of the package, so you'll havee it in node_modules/react-native-webrtc/tools/downloadBitcode.sh

I need to re-think how to handle bitcode a bit better, maybe by integrating this script or something. I'll keep this open.

Oh thanks, I will give a shot try.

Hi @saghul ,
It works.
But anytime I press on Hangup button (Leave room) in debug mode, it always show this log.

console.error:"[__filename]", "<_addOrRemoveAudioElement>:", "REMOVE_AUDIO_ELEMENT: no sound for id: PARTICIPANT_JOINED_SOUND"

Is it a bug?

You can ignore it.

Hi @saghul ,
Thank for that. But I have another question that Im trying to build sdk my own. It done. That what I do:

  • Build, file would be located in tmp/repo
  • I replace
allprojects {
    repositories {
        maven { url "file:/tmp/repo" }
        google()
        jcenter()
    }
}

And I put this line to app buildgradle:
implementation ('org.jitsi.react:jitsi-meet-sdk:+') { transitive = true }

But it got crash while I start jitsi view
Here is the log:

beginning of crash
2019-05-14 17:37:03.230 14448-15103/com.sns E/AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
    Process: com.sns, PID: 14448
    com.facebook.react.bridge.NoSuchKeyException: lineNumber
        at com.facebook.react.bridge.ReadableNativeMap.getValue(ReadableNativeMap.java:124)
        at com.facebook.react.bridge.ReadableNativeMap.getValue(ReadableNativeMap.java:128)
        at com.facebook.react.bridge.ReadableNativeMap.getInt(ReadableNativeMap.java:182)
        at com.facebook.react.util.JSStackTrace.format(JSStackTrace.java:28)
        at com.facebook.react.modules.core.ExceptionsManagerModule.reportSoftException(ExceptionsManagerModule.java:46)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158)
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:789)
        at android.os.Handler.dispatchMessage(Handler.java:98)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
        at android.os.Looper.loop(Looper.java:164)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
        at java.lang.Thread.run(Thread.java:764)

Please keep issues on topic. Open a new issue for this one.

I have the same issue, but node_modules/react-native-webrtc/tools/ contains only build-webrtc.py / ios_arch.js / release.sh. There is no downloadBitcode.sh

What version of the module are you using? That got added in 1.75.

My bad. I forgot that I'm relying on a fork. I needed to fork to make it work with mediasoup and I failed to make it work with the last version. Thanks for your answer. I'll try to find a solution.

I did make it work properly hehe.
Let me know what issue is.

@Sharcoux No worries. The 1.75 release contains a very important piece to make it work with mediasoup, AFAICT it should just work.

I know, but in practice, it didn't for me. But I'll get back into it as soon as I successfully upgrade my app to RN 60... I fixed the issue by running your script for the build M69.1.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rcidt picture rcidt  路  4Comments

jidanni picture jidanni  路  3Comments

galvaniccoffee picture galvaniccoffee  路  3Comments

TopheC picture TopheC  路  3Comments

ralgozino picture ralgozino  路  3Comments