[Bug] UIWebView Apple Deprecation April 2020 #9823
Comments
|
@EdoardoCinelli Do you have the linker behavior set to "SDK Only" or "Link All" for the Release|iPhone configuration? |
hartez
added
the
s/needs-info ❓
|
I also followed the link as well and I am still getting that message. below is also the cs.proj for my app if that will help out any at all. The linker is set to be link framework sdk's only and I added "--optimize=experimental-xforms-product-type" to the mtouch argumants.
|
|
@mharrisonbit I think the same as @hartez mentioned applies to you. In the
Of course make sure you do that for the right build configuration, use the comboboxes in the top of the screen for that |
|
I've tryed both but i'm still receving the mail from apple. Can one of this contain a reference to uiwebview? |
|
@EdoardoCinelli it looks like the Firebase one is referencing UIWebView and they are working on it: xamarin/GoogleApisForiOSComponents#369 |
|
@mharrisonbit just to update the others; we have chatted offline a bit, you seem to have all the right versions and settings, but still doesn't seem to work. You already sent me a list of NuGets as well, could you please add that here? So we can see if there is anything in there that might cause trouble. |
|
Hi! I have the same issue. We chatted a bit by mail with @jfversluis, and now I will continue this here. Here is my list of NuGets if it helps: |
|
I'm using AppCenter to build and publish on testflight. I didn't write it before. I removed all the firebase reference from code and NuGet and i'm still receving the mail. Is AppCenter the probolem? |
|
@EdoardoCinelli could you check your build configuration on App Center?
Make sure you have selected the Xamarin.iOS 13.10 version to build your app |
|
|
|
@jfversluis here are the nugets that I am using in the iOS project, I am hoping this will help figure something out. Again thanks everyone for the help. Also this is all being archived on my local and then pushed to the play stores. |
|
@jfversluis here are the NuGets that we are using: |
|
Alright, it looks like a number of you are using the Material visual which depends on MaterialComponents. The latest stable version is 72.2.0.1 but I came across this issue xamarin/XamarinComponents#745 which states that the reference to Check if you are actually using Material in your project. If not, try to remove the reference or add the 92.0.0-rc1 (or rc2) to your project manually and see if that fixes it. For the people who are (also) building on Azure DevOps, please beware that you might not be building against Xamarin.iOS 13.10. Check your logs to see if there is any output that states that the |
|
For the ones on Azure DevOps, follow the link underneath and set the Mono version to 6_6_1, that builds against Xamarin.iOS 13.10 |
|
Also tested without Appcenter and without firebase, webview, xamarin materials and xamarin essential and i'm still receving the mail. Can someone tell me what is going on? How can i check if i have some reference? |
|
I tried removing these are the NuGets that we are using: |
|
@Flaviocrtt After removing the nuget, please make sure to do the "bin/obj dance". Remove the bin and obj folder from your project and make sure to do a full rebuild so nothing cached gets stuck in there. Also, how are you building your app? Azure DevOps, App Center, manually? Are you sure you have all the right settings in place? |
|
I just created a build and I didn't get that message, I didn't make any changes to the nuget packages that are referenced just some design changes that were asked for. |
|
@mharrisonbit what do you mean exactly by "design changes"? |
|
No major changes just some margin in a couple views. I didn't add or remove any elements(labels, buttons, etc) to any view. |
|
OK, that is... strange. Maybe suddenly for this build some bits fell into place and you got a proper binary? Anyway, glad to see it's resolved! :) |
|
I know how my luck is and this was just a one time thing. lol I hope that everything just fell into place and I am good to go from here on out. I thank everyone for all the help. |
|
@jfversluis It worked, I removed Xamarin.Forms.Visual.Material, cleaned the solution, removed the bin and obj folders, and even restarted visual studio and macMini by guarantee. |
|
Great @Flaviocrtt! Thanks for letting us know! I think the update for the material things are already in progress. If you want to use them right now, just install it again but update the MaterialComponents NuGet on your iOS project to the latest pre-release. Again clean all the bin and obj stuff, but that should work and let’s you use material :) |
|
@EdoardoCinelli seems like we got most of the people here to get it working, did you also? |
|
Hi @biapar you’re totally right. And you should not be blocked by this, because the solution we have in place has also been here for a few months now for you. And it has been proven that it works each time. Let me know what doesn’t work for you and we can figure it out |
I already made everything ( in RELEASE mode ). I'll try again step by step.
=== Visual Studio Community 2019 for Mac === Version 8.5.5 (build 7) === Mono Framework MDK === Runtime: === Roslyn (Language Service) === 3.5.0-beta4-20125-04+1baa0b3063238ed752ad1f0368b1df6b6901373e === NuGet === Versione: 5.4.0.6315 === .NET Core SDK === SDK: /usr/local/share/dotnet/sdk/3.1.200/Sdks === Runtime di .NET Core === Runtime: /usr/local/share/dotnet/dotnet === Xamarin.Profiler === Versione: 1.6.12.26 === Updater === Versione: 11 === Apple Developer Tools === Xcode 11.4.1 (16137) === Xamarin.Mac === Version: 6.16.0.13 (Visual Studio Community) === Xamarin.iOS === Version: 13.16.0.13 (Visual Studio Community) === Xamarin Designer === Version: 16.5.0.471 === Xamarin.Android === Versione: 10.2.0.100 (Visual Studio Community) Versione di SDK Tools: 26.1.1 Informazioni sulla compilazione: === Microsoft Mobile OpenJDK === Java SDK: /Users/biagioparuolo/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_8.0.25 === Android SDK Manager === Version: 16.5.0.39 === Android Device Manager === Version: 16.5.0.73 === Xamarin Inspector === Version: 1.4.3 === Build Information === Release ID: 805050007 === Operating System === Mac OS X 10.15.4 === Enabled user installed extensions === Xamarin.Forms HotReload extension 1.4.0 |
|
Did you also actually submit a build to the App Store? I think there are some cases where the warnings in the output might give false positives. Also, are you archiving your app through Visual Studio for Mac or are you doing it through App Center or Azure DevOps by any chance? |
|
@biapar your other option is to comb through your app output to locate what is still referencing UIWebView #9823 (comment) |
I use Visual Studio on Mac and Windows. |
--optimization=force-rejected-types-removal results in mono error Unknown command line argument
Wow nice one!
Anyway i managed to pass it to AppStore with the following:
|
I've opened a PR on that doc to fix that. There is a couple of more people that approached me with it now working, but unfortunately it's not merged yet. Glad to hear you fixed it though! |
|
@jfversluis I have same problem with this UIWebView Deprecation issue.
But I still get the UIWebView Deprecation issue message from Apple when I pushed a new build to testflight. Could you tell me what's I am missing? What should I to do to fix this issue. My project have a reference to other library project, which is a Visual Studio project, it generated a library be used in this project. Below are my project's nuget package list. |
|
Hey @W0126 could you please try the grep suggestion from this comment and let me know what the outcome is from that? Also, make sure that you clear the bin/obj folders to make sure there is no caching involved. Double-check that you have configured the flag and settings for the right build configuration and that that is also the build configuration that you are using on any CI/CD system you might have in place. |
|
I did a grep command for my App. the uPyxis is my App. But I do not use UIWebView in my code. I have no idea where the UIWebView come from. I sure that I cleaned all bin/obj folders and all configuration have correct configured with the flag and settings. |
|
@jfversluis Thanks. |
|
That is great news @W0126! Let me know how it goes! |
|
Hi, I am developing apps using XF for last 5 years. Then I walked through this link https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/ By changing LinkAll I am facing serious issues with Signalr I am not able to use the signalr functionality If I change the linking option to LINK ALL. ERROR A suitable constructor for type 'Microsoft.AspNetCore.Http.Connections.Client.HttpConnectionFactory' could not be located. Ensure the type is concrete and services are registered for all parameters of a public constructor. I tried to use skip option but no luck. --linkskip=Microsoft.AspNetCore I am disappointed that Xamarin is not capable to help the developers. If someone has any solution so please help me out . |
|
@LumiProj did you by any chance try to set the Linker Behavior to SDK Only? |
|
I solved to update again each packages ( they was updates -1 version ) and made again the steps. |
|
Hi, I am also facing issues and have tried the suggested fixes mentioned above. I tried Link Sdk and Link All with these tags When I try I don't explicitly use any UIWebView in my project (Search in VS doesn't reveal anything) This is my configuration I've been looking through different examples and various forums over the past several days and none of them are able to remove the mentions in the binary files when I |
|
Hi, Finally I am in good shape. |
Thank you so much jmichas. |
|
Have the same problem. And the Answer is CALABASH! and the Xamarin TestCloudAgent nuget package. |
|
@pmace great you found the solution. In any case, the Calabash package should always be removed from the build going to the App Store since it uses private APIs that Apple won't allow anyway :) |
|
For anyone finding this: give Xamarin.Forms 5 (pre-release atm) a shot, that has the UIWebViewRenderer removed and should get you out of this trouble without any build flags or other hassles |
I have this same problem :( , @JJwilkin did you resolve it? |
|
@jmatusburgos please post the details of your project of send me an email directly |
|
@jmatusburgos Follow this should work. |
|
Hi @LumiProj Im have that arguments. @jfversluis Im use Xamarin.forms 4.8.0.1364. I'm had unistall many libraries like googleAnalytics and Google.SigIn that gave me references to UIWebView and Im upgraded anothers until the command grep dont show me reference on some library, but now when I use I'm use VS2019 on microsoft machine and mac with XCode 12. this is my configuration:
|
|
@jmatusburgos could you maybe find my email on my GitHub page and reach out there so we can figure this out? :) |
|
@jfversluis thanks for you response, I want comment you that with help of my co workers we found 3 libraries that caused the issue : Refractored.XamForms.PullToRefresh 2.4.1 All these libraries are obsolete . We have removed and finally works. So sometimes can be a jigsaw found the guilty libraries. again, thanks @jfversluis for you'r availability :) |
|
Yeah I think because they are including native libraries that they created a wrapper around that is not picked up by that grep command. Sorry for the trouble, glad you figured it out! |
and others
Before commenting on this issue please read the following comment and documentation links
#9823 (comment)
And refer to the following official documentation links
https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/
https://docs.microsoft.com/en-us/xamarin/ios/release-notes/13/13.16#help-with-uiwebview-deprecation
Original Issue Description
I've installed the 4.5.0.356 of xamarin and using testflight to release my app on iOS. I have xamarin form 4.5 and implemented everything link in the documentation
https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/webview?tabs=windows#uiwebview-deprecation-and-app-store-rejection-itms-90809
https://docs.microsoft.com/en-us/xamarin/xamarin-forms/release-notes/4.5/4.5.0
I still receve the message from apple:
"Dear Developer,
We identified one or more issues with a recent delivery for your app, "XXXXXXXX" 3 (46). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs starting from April 2020 . See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can upload a new binary to App Store Connect.
Best regards,
The App Store Team"
Can someone help me to fix this problem?
Here is my csproj
The text was updated successfully, but these errors were encountered: