App is crashing during zoom sdk initialization (Android app)

Meeting SDK Android
1

Hello,

We are facing an issue on some devices. The app is crashing during zoom SDK initialization.

We are using zoom android SDK version 4.6.21666.0429 and we receiving a crash on load crypto_sb lib file on few devices.
Crash line is - System.loadLibrary(“crypto_sb”) on AppContext.class file

I am sharing the device detail bellow.

OS - Android
Version - 5.1.1
Manufacturer - OPPO
Model - A37f
DPI - xhdpi

Which version?
4.6.21666.0429

Smartphone (please complete the following information):

  • Device: Oppo A37f
  • OS: Android
  • Version 5.1.1
2

Hello support team,

I’m also facing this issue.
All information provided by Namrata is exactly of my issue.

My debugger console showing this error
Disconnected from the target VM, address: ‘localhost:8600’, transport: ‘socket’

please provide some solution.

3

Hi,

Could you provide a logcat log for the issue you are facing? You could get the logcat log by using adb logcat>log.txt and provide the log.txt to us for further investigation. Thanks!

4

Hi Carson,

Thanks for reply.

Here I am sharing the log:

06-04 14:01:41.880 W/linker (15858): /data/app/**.****.app-1/lib/arm64/libzoom_stlport.so: unused DT entry: type 0x6ffffffe arg 0x218a8
06-04 14:01:41.880 W/linker (15858): /data/app/**.****.app-1/lib/arm64/libzoom_stlport.so: unused DT entry: type 0x6fffffff arg 0x3
06-04 14:01:41.880 W/linker (15858): Unsupported flags DT_FLAGS_1=0x9
06-04 14:01:41.880 W/linker (15858): /data/app/**.****.app-1/lib/arm64/libcrypto_sb.so: unused DT entry: type 0x6ffffffe arg 0x39518
06-04 14:01:41.880 W/linker (15858): /data/app/**.****.app-1/lib/arm64/libcrypto_sb.so: unused DT entry: type 0x6fffffff arg 0x2
06-04 14:01:41.960 E/PSD ( 348): set_ps_threshold: low_thd 143 high_thd 183 ps:63 crosstalk:58 state:1
06-04 14:01:41.990 I/WindowState( 956): WIN DEATH: Window{9b804a5 u0 **.****.app/**.****.app.MainActivity}
5

Hi @carson.zoom
Here are logs from Android Studio logcat at warn level

06-04 09:18:54.160 2259-3981/? W/InputDispatcher: channel ‘128a423e net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’ ~ Consumer closed input channel or an error occurred. events=0x9
06-04 09:18:54.170 2259-3981/? E/InputDispatcher: channel ‘128a423e net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’ ~ Channel is unrecoverably broken and will be disposed!
06-04 09:18:54.170 2259-3981/? W/InputDispatcher: channel ‘3619d5c0 net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’ ~ Consumer closed input channel or an error occurred. events=0x9
06-04 09:18:54.170 2259-3981/? E/InputDispatcher: channel ‘3619d5c0 net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’ ~ Channel is unrecoverably broken and will be disposed!
06-04 09:18:54.170 2259-4775/? W/InputDispatcher: Attempted to unregister already unregistered input channel ‘3619d5c0 net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’
06-04 09:18:54.180 2259-9392/? W/InputDispatcher: Attempted to unregister already unregistered input channel ‘128a423e net.ezeon.eisdigital/net.ezeon.eisdigital.livestream.ZoomMeetingActivity (server)’
06-04 09:18:54.220 2259-4831/? W/ActivityManager: Force removing ActivityRecord{34f28854 u0 net.ezeon.eisdigital/.livestream.ZoomMeetingActivity t225}: app died, no saved state
06-04 09:18:54.220 2259-4831/? W/ActivityManager: Force removing ActivityRecord{2bf45589 u0 net.ezeon.eisdigital/.livestream.LiveStreamingListActivity t225}: app died, no saved state
06-04 09:18:54.340 4248-4963/? W/ResourceType: No package identifier when getting value for resource number 0x00000000
06-04 09:18:54.340 4248-4963/? W/PackageManager: Failure retrieving resources for net.ezeon.eisdigital: Resource ID #0x0
06-04 09:18:54.610 15787-15812/net.ezeon.eisdigital E/SQLiteLog: (283) recovered 22 frames from WAL file /data/data/net.ezeon.eisdigital/databases/androidx.work.workdb-wal
06-04 09:18:54.620 259-532/? E/Vold: Failed to find mounted volume for /storage/sdcard1/Android/data/net.ezeon.eisdigital/files/
06-04 09:18:54.620 259-532/? W/Vold: Returning OperationFailed - no handler for errno 0
06-04 09:18:54.620 259-532/? W/FrameworkListener: Handler ‘volume’ error (Success)
06-04 09:18:54.620 15787-15787/net.ezeon.eisdigital W/ContextImpl: Failed to ensure directory: /storage/sdcard1/Android/data/net.ezeon.eisdigital/files

6

Hi @mdsafdarsaleem,

Thanks for the reply and the log info. We are able to identify an issue and we will fix this in the next release.

Thanks!

7

Hi @carson.zoom,

This is great news. When is the next release expected? And is there a workaround till then as Zoom is unusable till we get the next release.

8

Can you share, when this release is going to be?

10

Hello zoom support team,

We also facing same issue.

please provide release or patch as soon as possible…

Thank You…

1 Like
11

Please consider providing a patch. Hundreds of users are suffering because of this issue. This is very urgent.

Thanks.

12

Hi @carson.zoom,
Even in our case very few users are facing the issue while initialisation is happening. But for most of the users, the initialisation is happening properly. Can anyone justify if this might be case of version. My project minSdk version is 21 and targetSdkVersion is 29. Please consider this as priority and let me know

13

Hi everyone,

Could you provide the device information of the device that has this issue? Is everyone facing this issue with Oppo A37f?

14

Hi @carson.zoom

Yes, every device with Oppo A37f is facing this issue.! Attaching one of the device pics

WhatsApp Image 2020-06-10 at 1.23.04 PM|281x500

15

@carson.zoom yes , most of the user who are facing are having Oppo A37f

16

We are facing the issue in these two devices.

  1. Oppo A37F
  2. Vivo Y51L
17

Yes, both these devices are giving issues.

18

Hi All,

This issue is now almost 2 weeks old. Because of this issue, Zoom SDK is unusable. This is high priority issue. Can the team update when the issue will be resolved. We cannot have 2-3 weeks to resolve business impacting issues?

19

Hi,

Thanks for the device information. It seems like this issue is only happening with Oppo A37F and Vivo Y51L(They are using the same CPU), not happening for all other devices.

We are targeting to have a release very soon(tentative date: next week), and this issue will be fixed in the next release.

Thanks!

20

Thanks a lot for looking into the issue, I much appreciate your efforts. It would be great if you can share a release date in upcoming days.

21

Hello Team,

As you already told in last week that in upcoming week you release the update but today is the last day of the week but still we have not received the resolutions of this problem so i am request you to please release the update for this problem resolutions.

Thank You…