Christian Sousa
10/26/2020, 10:43 AMUIWebView
that Apple announced: https://developer.apple.com/news/?id=12232019b
Running the following command on our binary
for framework in Frameworks/*.framework; do
fname=$(basename $framework .framework)
echo $fname
nm $framework/$fname | grep UIWebView
done
We get the following output:
0000000000990190 s __OBJC_LABEL_PROTOCOL_$_UIWebViewDelegate
00000000009e64a0 d __OBJC_PROTOCOL_$_UIWebViewDelegate
Which means that our SDK does have references to UIWebViewDelegate, but this is not in use and this is a potential roadblocker for every iOS app integrating the SDK.
Also, when trying to upload a sample app we get the warning about the usage of UIWebView
.
As far as I can understand, the interop lib includes these references for legacy reasons or something like that.
What would be our best solution for this issue? Or are there any plans on removing the UIWebView
from the KMP Lib?
Thanks a lot! 🙂svyatoslav.scherbina
10/26/2020, 2:52 PMAlso, when trying to upload a sample app we get the warning about the usage ofÂCould you please share the exact warning message?.UIWebView
Which means that our SDK does have references to UIWebViewDelegateApple doesn’t mention this protocol in their announcement. Are you sure this warning is caused by references to UIWebViewDelegate? It is not even deprecated: https://developer.apple.com/documentation/uikit/uiwebviewdelegate?language=objc
svyatoslav.scherbina
10/28/2020, 8:54 AMUIWebViewDelegate
doesn’t cause any problems.
Adding UIWebView
does cause validation failure. But Kotlin-produced frameworks don’t have it unless you explicitly use it.
So, without more information from you (for example, exact message from Apple) I can’t advice you any solution at all.