-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No visible @interface for 'MobileRTC' #20
Comments
Hi @Palwisha77 the issue is a breaking change in the SDK, are you using the scripts provided by this library to import the SDK or manually downloading them? |
I have downloaded the SDK manually from the link provided in the library. The following are the versions that I am using in my project. |
Try with this version v4.6.21666.0428 download it from here ios-dev: https://github.com/zoom/zoom-sdk-ios/archive/v4.6.21666.0428.zip put them in Tell me if it worked. |
@Palwisha77 Iv'e pushed a fix to the library version 1.0.17 and changed the SDK import bash files to download previous working version v4.6.21666.0428. I will update the library to work with the latest SDK when I get the chance. |
Thank you I will try this and let you know if it works. |
@chaimPaneth I used the library version 1.0.17 and SDK version v4.6.21666.0428 the build is successful but the app won't install in device. The provisioning profile and signing certificates are correct as the app was installed successfully without the SDK but after integrating the SDK app won't install. Is there any signing issue in SDK or Frameworks? I don't understand the issue. |
@Palwisha77 when installing on a real device you have to use the prod SDK and when running in the simulator you have to use the dev SDK thats why there are two bash scripts for iOS make sure you use the correct one. 1: Import (correct) SDK using bash file |
Thank you for this I have used dev SDK and trying to install it on the device. |
Tell me if it works with the prod SDK |
@Palwisha77 the Failure Reason mentions "No code signature found." there is probably an issue with your code signing, when installing to a device from xcode you need a development certificate not adhoc or production also setting it on auto signing might help. |
@chaimPaneth I think my certificates are correct because the app is installing on the IOS device successfully without the SDK but after integrating I got this issue. |
Can you try removing the library |
@chaimPaneth as u said I unliked the library and run the app on a real device. App installed successfully. |
@Palwisha77 did you install the production SDK before running the app on a real device, check this out https://github.com/chaimPaneth/react-native-zoom-bridge#sdk-type.
Rerun project. |
Yes, I have tried both dev SDK and prod SDK and got the same issue with both SDK types. |
I have checked this https://stackoverflow.com/questions/38371044/ios-app-testing-app-installation-failed-no-code-signature-found but my Xcode version is 11.3.1 (11C504). I didn't find any 'Embed Frameworks' under 'Build Phase' |
Hi @Palwisha77 Can you try and archive an .ipa with AdHoc provision and upload it to Microsoft AppCenter and install from there? Tell me if archiving worked? |
No, I have not try archiving but soon will tell you. |
Just wanted to note I'm having the same issue. |
me too but you can run it with archiving and install from Microsoft AppCenter |
I was able to get it to work in dev on a locally tethered device by removing the reference to |
This worked for me 💯 |
This issue occured again for me recent build. I fixed it by following steps
👍 |
It's not work for me. Anyone have other solution beside this. ? `Details Unable to install "testingapp"
|
I have recreated the project and run the command "pod install" then remove incorrect headers from all SDK files after that I build the project and getting the error "No visible @interface for 'MobileRTC' declares the selector 'setMobileRTCDomain:'".
Please help me in this I am trying to integrate IOS SDK for the last 3 to 4 days but still unable to integrate.
The text was updated successfully, but these errors were encountered: