Afnetworking: appstore审核提示用了UIWebView的api,被拒绝

Created on 12 Sep 2019  ·  25Comments  ·  Source: AFNetworking/AFNetworking

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.
请问能更新代码把UIWebView分类去掉么

Most helpful comment

We don't see any of the pull requests has been approved to fix this issue? When can we expect to see this issue to be resolved?

Any ideas @kcharwood @mattt @Kaspik

All 25 comments

我也刚刚遇到这个问题

We don't see any of the pull requests has been approved to fix this issue? When can we expect to see this issue to be resolved?

Any ideas @kcharwood @mattt @Kaspik

I've also received the same warning from Apple. When shall we fix this issue?

From Apple:

Dear Developer,We identified one or more issues with a recent delivery for your app, 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 . See https://developer.apple.com/documentation/uikit/uiwebview for more information.After you've corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.

It's just a warning, I can upload my app with the warning.

It's just a warning, I can upload my app with the warning.

But I am afraid that manual review will be affected,I've heard that some people have been turned down for this warning

Is anybody got approved from apple reviewer with this warning?

我也收到了,不知道苹果是怎么检测的

I got my app approved last week with UIWebview. But I am working on replacing UIWebView with WKWebView for upcoming release.

I delete the UIWebView+AFNetworkingcategory , but it seems not working.

only a warning, our app has been reviewed.

@Xianyus As of now, Apple won't reject the build. But going forward this needs to be addressed.

Hey everybody, #4439 is available and passing all CI tests. We have one dependency on one of our projects that uses this lib so we would like to see this addressed and a new version of AFNetworking pushed out.
Does anybody here have a direct comm channel with one of the maintainers?
Thanks!

Hey everybody, #4439 is available and passing all CI tests. We have one dependency on one of our projects that uses this lib so we would like to see this addressed and a new version of AFNetworking pushed out.
Does anybody here have a direct comm channel with one of the maintainers?
Thanks!

From the information on the release page,some of the latest release versions were released by SlaunchaMan,maybe @SlaunchaMan can help release a new version.

Thank you @Daemonson, I'm going to reach out to @SlaunchaMan and see what needs to be done to push #4439 out.

@tjanela Any update from SlaunchaMan on this?

AFNetworkin , BlockKit 删除其中的分类即可

@tjanela Any update from SlaunchaMan on this?

No, haven't heard back from any of the listed maintainers, nor from the Alamofire team.

Still no traction on this? Looks like #4439 is close.

@knarf74, things are pretty close. I managed to break #4439 into digestible chunks as requested by the maintainers. It’s up to them now.

Why is this taking so long?

这个只是警告,并不会影响正常上线,我们的APP 已经审核通过了

------------------ 原始邮件 ------------------
发件人: "Jacek Dogiel"<[email protected]>;
发送时间: 2019年10月31日(星期四) 下午4:50
收件人: "AFNetworking/AFNetworking"<[email protected]>;
抄送: "Casper ????????"<[email protected]>; "Comment"<[email protected]>;
主题: Re: [AFNetworking/AFNetworking] appstore审核提示用了UIWebView的api,被拒绝 (#4436)

Why is this taking so long?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@tjanela still not looking good. lost traction with #4439?

Hey @knarf74, it seems like @jshier got his attention steered elsewhere.
I would love to see this #4439 released, as the community has invested in this a lot.
Despite the warning around AFNetworking being replaced by newer approaches, it is still widely used and, as such, would warrant some form of LTS. I guess it's either maintaining our own forks or waiting for a release.

See #4439

Updated, released. Can be closed.

Was this page helpful?
0 / 5 - 0 ratings