Post

Replies

Boosts

Views

Activity

Question about simulating BGAppRefreshTask and BGProcessingTask in recent Xcode versions
ご指定の挨拶や結びの言葉をすべて除外した、本文のみの英文です。 I am writing to inquire about the debugging workflow for background processing in recent versions of Xcode. In previous versions of Xcode, we were able to test the behavior of background fetches using the "Simulate Background Fetch" option under the Debug menu. However, this menu item is no longer available in the latest Xcode environment. Our application requires executing background tasks, such as automatically transferring images captured during background transition to a remote server. We are currently in the process of migrating our background structure to the latest BackgroundTasks framework (BGTaskScheduler) in accordance with the recommendations in the official documentation. Now that the GUI menu item has been removed, could you please provide the official guidelines or recommended workflow for simulating and debugging BGAppRefreshTask and BGProcessingTask on the iOS Simulator? Specifically, I would like to know if executing specific LLDB commands while the process is paused is the only supported method to simulate these events during development.
0
0
55
3d
How to Publish an iOS 17+ Only App on the App Store and Pre-Release Verification Steps
What I Want to Achieve I want to create an app that only supports iOS 17 and later, making it unavailable for display, installation, or updates on the App Store for devices running iOS 16 or earlier. Implementation Details I have applied the following settings: Xcode ・Build Settings → Deployment  iOS Deployment Target: iOS 17 ・General → Minimum Deployments  iOS 17 ・AppFrameworkInfo.plist MinimumOSVersion 17.0 ・Podfile config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '17.0' By building and releasing the app with these settings, will it ensure that the app is only available for iOS 17 and later? Additionally, is there a way to verify this before release? I am considering using TestFlight to publish an app that only supports iOS 18 and testing the installation on an iOS 17 device. Would this method allow me to confirm that the restriction is working as intended?
0
0
128
Mar ’25
Question about simulating BGAppRefreshTask and BGProcessingTask in recent Xcode versions
ご指定の挨拶や結びの言葉をすべて除外した、本文のみの英文です。 I am writing to inquire about the debugging workflow for background processing in recent versions of Xcode. In previous versions of Xcode, we were able to test the behavior of background fetches using the "Simulate Background Fetch" option under the Debug menu. However, this menu item is no longer available in the latest Xcode environment. Our application requires executing background tasks, such as automatically transferring images captured during background transition to a remote server. We are currently in the process of migrating our background structure to the latest BackgroundTasks framework (BGTaskScheduler) in accordance with the recommendations in the official documentation. Now that the GUI menu item has been removed, could you please provide the official guidelines or recommended workflow for simulating and debugging BGAppRefreshTask and BGProcessingTask on the iOS Simulator? Specifically, I would like to know if executing specific LLDB commands while the process is paused is the only supported method to simulate these events during development.
Replies
0
Boosts
0
Views
55
Activity
3d
How to Publish an iOS 17+ Only App on the App Store and Pre-Release Verification Steps
What I Want to Achieve I want to create an app that only supports iOS 17 and later, making it unavailable for display, installation, or updates on the App Store for devices running iOS 16 or earlier. Implementation Details I have applied the following settings: Xcode ・Build Settings → Deployment  iOS Deployment Target: iOS 17 ・General → Minimum Deployments  iOS 17 ・AppFrameworkInfo.plist MinimumOSVersion 17.0 ・Podfile config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '17.0' By building and releasing the app with these settings, will it ensure that the app is only available for iOS 17 and later? Additionally, is there a way to verify this before release? I am considering using TestFlight to publish an app that only supports iOS 18 and testing the installation on an iOS 17 device. Would this method allow me to confirm that the restriction is working as intended?
Replies
0
Boosts
0
Views
128
Activity
Mar ’25