iOS App rejected by apple for violating Guideline 2.5.1 - Performance - Software Requirements | Flutter 3.35.x seems to use non-public or deprecated APIs

[Abhiraj3112000]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Recently our iOS app built using Flutter versions 3.35.1 and 3.35.7 were rejected by Apple upon review. Apple states the following reason:

Guideline 2.5.1 - Performance - Software Requirements

The app uses or references the following non-public or deprecated APIs:

Frameworks/flutter_inappwebview_ios.framework/flutter_inappwebview_ios
Classes:
• PGHostedWindow

Runner
Classes:
• __SwiftValue

The use of non-public or deprecated APIs is not permitted, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms.

Next Steps

It would be appropriate to revise your binary and remove any references to the non-public or deprecated APIs identified above.

If you are using third-party libraries, update to the most recent version of those libraries. If you do not have access to the libraries' source, the following command line tools can help you identify the location of problematic code:

• The "strings" tool can output a list of the methods the library calls.
• The "otool -ov" tool will output the Objective-C class structures and their defined methods.

Note:
Earlier iOS app with Flutter version 3.27.3 was approved and never faced this issue.
XCode Version used: 26.2.0

Expected Behavior

The submitted build should get accepted in AppStoreConnect.

Steps with code example to reproduce

General usage of FlutterInAppWebview.

Stacktrace/Logs

NA

Flutter version

v3.35.7

Operating System, Device-specific and/or Tool

iPad Air 11-inch (M3) - tested by apple team.

Plugin version

v6.1.5

Additional information

NA

Self grab

• I'm ready to work on this issue!

[prasanna-tapzo]

Our iOS app got rejected today. Apple flagged non-public / deprecated iOS API usage (possibly related to internal WebKit window handling such as PGHostedWindow), causing a Guideline 2.5.1 rejection when using this plugin on Flutter 3.29.x. Requesting a compliant fix or workaround to unblock App Store submission.

[Abhiraj3112000]

@prasanna-tapzo as a temporary workaround, I added a pre-action in the build phase of the respective scheme in Xcode to manually remove this symbol string, which resolved Apple’s PGHostedWindow detection during review.

However, in my case they are still rejecting it quoting the __SwiftValue reference.

[imHarshBhatia]

@Abhiraj3112000 , as mentioned by @prasanna-tapzo , we are facing the same issue of mention of exactly the 2 issues mentioned by you. Removing the PGHostedWindow would be a workaround but the __SwiftValue reference will still be an issue for us as well.

What has been your approach for the work around of this issue?

[Abhiraj3112000]

@imHarshBhatia since __SwiftValue is not something we directly call or reference, hence, we’re unable to apply any workaround for this.
We have raised this issue on the official Apple Developer Forum (thread 811110), and Apple has responded that they are currently investigating the matter.

[imHarshBhatia]

Hi @Abhiraj3112000 , Thanks for clarifying the details. Will it also be possible for you to share the pre-action details which you have added in XCode so that I can have a better understanding of the same?

[Abhiraj3112000]

For reference, the __SwiftValue issue has been raised in the firebase-ios-sdk repo, they will be releasing a new version which will solve this.

Issue link - firebase/firebase-ios-sdk#15639

[richirisu]

@pichillilorenzo
I can see that this issue has been fixed in the current beta branch. May I ask, do you already know when you will release it to the official package repository?