Post

Replies

Boosts

Views

Activity

Is our understanding of the iPhone Duo requirements correct?
Hello, We're preparing guidance about iPhone Duo for our team and clients. Could someone confirm whether the following understanding is correct? Starting April 2027, apps uploaded to App Store Connect must be built with the iOS 27 SDK or later. Apps built with the iOS 27 SDK are resized on iPhone Duo, and there's no way to keep the compatibility presentation (the app shown at its previous size in the center of the inner display). So any app update submitted after April 2027 will be resized on iPhone Duo. Starting April 2027, apps using the iOS 27.1 SDK or later must include iPhone Duo screenshots. Under the guidance for Guideline 2.3.3, the majority of screenshots for each device must show the app in use on that device, and screenshots must not misrepresent the app's actual interface. So iPhone Duo screenshots need to be captured from the app actually running on iPhone Duo or the iPhone Duo simulator, not mocked up or resized from other iPhone screenshots. If App Review finds that an app's UI is broken on iPhone Duo and can't be operated (for example, buttons can't be tapped), the app may be rejected under Guideline 2.1(a), in the same way iPhone-only apps have been rejected for issues found on iPad. If any part is inaccurate, we'd appreciate a correction. References: https://developer.apple.com/iphone-duo/prepare/ https://developer.apple.com/forums/thread/847836 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications https://developer.apple.com/help/app-review/guideline-reference/2-3-3-screenshots Thank you.
1
2
292
1w
Suddenly being asked for export compliance, even with ITSAppUsesNonExemptEncryption set to NO
Hello everyone, I've encountered an issue with export compliance on App Store Connect that I haven't seen before. In my Info.plist, I have always set the ITSAppUsesNonExemptEncryption key (formerly App Uses Non-Exempt Encryption) to NO. In the past, this was sufficient to bypass the export compliance questions when submitting a build. However, with my most recent submission, I am now being prompted to answer these questions. Nothing has changed in my app's encryption usage. Has there been a recent change in policy or a system-wide issue that would cause this change in behavior? Is anyone else experiencing this? Thank you for your help.
3
0
244
Oct ’25
Are there exceptions for ITSAppUsesNonExemptEncryption = NO?
My app has ITSAppUsesNonExemptEncryption set to NO, but I am still required to answer the export compliance questions. Are there any specific conditions, APIs, or frameworks (like WKWebView or third-party SDKs) that are known to override this Info.plist setting and force a compliance review? I'm trying to understand what triggers this requirement even when the key is set to NO. Is there any documentation on this?
0
0
127
Oct ’25
Is our understanding of the iPhone Duo requirements correct?
Hello, We're preparing guidance about iPhone Duo for our team and clients. Could someone confirm whether the following understanding is correct? Starting April 2027, apps uploaded to App Store Connect must be built with the iOS 27 SDK or later. Apps built with the iOS 27 SDK are resized on iPhone Duo, and there's no way to keep the compatibility presentation (the app shown at its previous size in the center of the inner display). So any app update submitted after April 2027 will be resized on iPhone Duo. Starting April 2027, apps using the iOS 27.1 SDK or later must include iPhone Duo screenshots. Under the guidance for Guideline 2.3.3, the majority of screenshots for each device must show the app in use on that device, and screenshots must not misrepresent the app's actual interface. So iPhone Duo screenshots need to be captured from the app actually running on iPhone Duo or the iPhone Duo simulator, not mocked up or resized from other iPhone screenshots. If App Review finds that an app's UI is broken on iPhone Duo and can't be operated (for example, buttons can't be tapped), the app may be rejected under Guideline 2.1(a), in the same way iPhone-only apps have been rejected for issues found on iPad. If any part is inaccurate, we'd appreciate a correction. References: https://developer.apple.com/iphone-duo/prepare/ https://developer.apple.com/forums/thread/847836 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications https://developer.apple.com/help/app-review/guideline-reference/2-3-3-screenshots Thank you.
Replies
1
Boosts
2
Views
292
Activity
1w
Suddenly being asked for export compliance, even with ITSAppUsesNonExemptEncryption set to NO
Hello everyone, I've encountered an issue with export compliance on App Store Connect that I haven't seen before. In my Info.plist, I have always set the ITSAppUsesNonExemptEncryption key (formerly App Uses Non-Exempt Encryption) to NO. In the past, this was sufficient to bypass the export compliance questions when submitting a build. However, with my most recent submission, I am now being prompted to answer these questions. Nothing has changed in my app's encryption usage. Has there been a recent change in policy or a system-wide issue that would cause this change in behavior? Is anyone else experiencing this? Thank you for your help.
Replies
3
Boosts
0
Views
244
Activity
Oct ’25
Are there exceptions for ITSAppUsesNonExemptEncryption = NO?
My app has ITSAppUsesNonExemptEncryption set to NO, but I am still required to answer the export compliance questions. Are there any specific conditions, APIs, or frameworks (like WKWebView or third-party SDKs) that are known to override this Info.plist setting and force a compliance review? I'm trying to understand what triggers this requirement even when the key is set to NO. Is there any documentation on this?
Replies
0
Boosts
0
Views
127
Activity
Oct ’25