stntz / Xamarin.ZoomBinding

Zoom Mobile SDK Binding for Xamarin Android and iOS(device only)
15 stars 13 forks source link

Android zoom sdk 5.9.1.3674 - build failure expected, see notes #35

Open AdamDiament opened 2 years ago

AdamDiament commented 2 years ago

Hi @stntz - I have fixed up all the metadata and the commonlib and mobilertc projects are now building.

Having said that, I tried to run through the change and recompilation steps, but I keep getting the errors in the xml files even when I think I have fixed all of them, and recompiled the mobilertc.aar file. Either there might be other errors lurking, or I might not be doing the recompilation step properly.

Please could you have a look at this final step for me? I raised an issue on the zoom developer forum, but as we know it might take them 18 months to fix it! I've left the values.xml files as they were, but written down issues I found below.

Values.xml issues I found

zm_accessibility_reacion_label_233717 - %s and %d zm_join_meeting_fail_dialog_msg_164409 - %s and %d zm_alert_remind_archived_content_meeting_267230 - bad whitespace character

Recompilation steps I tried in case I am missing a step you know about:

  1. Ran unzip mobilertc.aar -d tempFolder
  2. Changed some values files in temp folder, to add proper placeholders
  3. Ran jar cvf mobilertc.aar -C tempFolder/ .

I'm raising this into the xamarin5 branch for now

Thanks!

Adam

AdamDiament commented 2 years ago

Hi @stntz hope you're doing well. Do you have any idea what I did wrong in the recompile stage?

AdamDiament commented 2 years ago

Update - I got all of the placeholders and the recompilation working. I found some more missing placeholders. I used the script here to clean it up. I have raised a ticket with zoom here to fix for future versions.

All of the build failures to do with placeholder strings are fixed. The next problem to overcome is that there are missing resources from the exoplayer dependency. These are likely due to the fact zoom now requires v 2.13.3 of explayer core and UI. The latest xamarin binding is only 2.11. The library has not been updated in 2 years and the maintainer has no intention of continuing support according to the issues. They are awaiting a community contribution.

https://github.com/Baseflow/ExoPlayerXamarin

So we could either get into upgrading the exoplayer binding itself, or investigate a way to bypass these required resources.

image

AdamDiament commented 2 years ago

The Android project builds now, I have added fake exo resources for now to make this happen - without wanting to embark on a PR into the Exoplayer repo. There are still problems launching on an Android device, due to conflicts with android material versions and Xamarin forms. It is supposed to be fixed with the latest xam 5 support release, but I still get the issue. If you can provide any insight @stntz I would be grateful.

https://docs.microsoft.com/en-us/answers/questions/470766/shellitemrendererjava-error-when-building-android.html

https://github.com/MvvmCross/MvvmCross/issues/4268