Posts

Post marked as solved
2 Replies
283 Views
I have an independent Watch app in App Store Connect, not yet submitted for rewiew. I had some screenshots for an earlier build uploaded, but since in later builds I changed the UI, I removed the screenshots to add new ones. However, when I drag & drop the image files on the area in the App Store Connect, this does not work. All I see is the image file blurred, overlaid is a progress indicator which does not advance at all. Even if I wait like an hour or so. Same thing happens if I select the add screenshots link. When looking at Safari Inspector, I see HTTP 404 and 409 errors, related to some javascript with something related to app clips, but obviously this cannot be so since the watchOS app does not have app clips. Don't know if these details matter, but app is multilingual (three languages), Apple Watch app only, so no associated iOS app. I am able to provide builds through Archiver in Xcode. The app icon from the app assets do show up in the App Store Connect. Can this be an issue: I did first upload version 1.0.0 of the app. Then when adding new features, upgraded the version to 1.0.1 and removed the 1.0.0 from the App Store Connect. Can this cause the issue, and if yes, how can I fix this? I already sent a support request four days ago but haven't heard from Apple dev support yet.
Posted
by AndyJJ.
Last updated
.
Post marked as solved
4 Replies
407 Views
My independent watch app successfully initiates a background task with WKExtension.scheduleBackgroundRefresh and then uses URLSession and URLSessionConfiguration to launch a background download task URLSessionDownloadTask. This successfully completes, as I can see from the logs: file is downloaded into a temp file. Context: Xcode Version 12.0 beta 2, watchOS beta 2 in the Simulator (not on real device). This happens in my ExtensionDelegate when my app's complication is in the watch face. But then the download task is not completed in the URLSessionDownloadDelegate, since in the log com.apple.nsurlsessiond says: Will wake client com.organization.appname.watchkitapp.watchkitextension for session app-session-id-on-background if we receive a notification that it supports launch-on-demand So, how can I add support for launch-on-demand for my app and give the notification to satisfy nsurlsessiond? I've seen some discussions that this would work on a real device. However cannot test this yet on an Apple Watch with watchOS beta 7.
Posted
by AndyJJ.
Last updated
.