Post not yet marked as solved
Hints for solving the problem can be found on the following website.
iOS - UIImageView - how to handle UIImage image orientation
The code shown above works for displaying images, but it doesn't seem to work when converting to SKTexture.
To achieve this, it is effective to generate a UIImage using UIGraphicsBeginImageContext or to generate a UIImage using CGAffineTransformTranslate or CGAffineTransformRotate.
Post not yet marked as solved
It seems that the specifications of App Store Connect have changed since the review process for iOS17 compatible apps began.
If things remain as they are, the same problem will occur again.
To resolve, you need to also create an entitlements file in your WatchKit app and add the com.apple.developer.game-center key.
However, the WatchKit app does not have a Game Center option under Capability, so you cannot add Game Center.
Therefore, it is necessary to forcefully create an entitlements file.
Work procedure :
Xcode -> TARGETS -> Watch App -> Signing & Capabilites
Click +Capabilites and select available Capabilities.
Delete the Capability added in 2. above. This will create an entitlements file.
Open your Watch App's entitlements file and add the com.apple.developer.game-center key and set the Value to YES.
As a prerequisite, the Watch App profile must have Game Center enabled.
Additionally, Xcode15 now allows full automation and custom selection when validating and distributing.
I recommend choosing Custom here and making sure Game Center is enabled by specifying the profile explicitly, like when you were working with Xcode14.
Post not yet marked as solved
The root cause of this is that the message displayed on App Store Connect does not match the cause.
WatchKit extension allows you to enable Game Center and create entitlements plists.
WatchKit app does not allow you to select and enable Game Center, so you cannot create the entitlements plist.
However, provisioning profiles for WatchKit apps must be created with Game Center-enabled Identifiers.
Suppose your iOS app and WatchKit extension enabled Game Center in Signing & Capabilities and created an entitlements plist with com.apple.developer.game-center Key set to true.
However, if the provisioning profile for your WatchKit app uses Identifiers that do not have Game Center enabled, you will receive the same error message when submitting for review.
The real cause of this is that Game Center is not enabled in the provisioning profile for WatchKit App.
I think many developers were confused because the cause and the message display did not match.
Post marked as Apple Recommended
In my case, I got an error with Inon-public selectors instead of non-public AP during validation.
I didn't have this problem a month ago.
We have reported this to Apple using feedback assistance.
https://developer.apple.com/forums/thread/713574
Post not yet marked as solved
I am also encountering the same phenomenon.
This is caused by a selector in a third-party library that has the same name as an iOS private selector, but it does not occur in Xcode13, but in Xcode14.
I think it's probably a validation bug for iOS16.
As FB11488329 , I reported it to Feedback Assistant.
Post marked as Apple Recommended
I also encountered the same phenomenon.
However, depending on the loading URL, this message may or may not be displayed.
I'm not quite sure what the difference is.
When this message was not displayed, the following message was displayed.
Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
Xcode Version 14.0 beta 6 (14A5294g)
iOS16.0 beta 8
iPhone SE 2generation
Post not yet marked as solved
I am also having the same problem.
This warning is creepy, even though the device seems to work fine.
Xcode Version 14.0 beta 6 (14A5294g)
iPad Air 4Generation iPadOS 16 beta7
iPhoneSE 2Generation iOS 16 beta7
Three weeks after the phenomenon occurred, it started to operate normally.
The delegate of SKProductsRequest is called.
It is probable that the sandbox system failure was prolonged.
If your code is okay and your in-app purchase settings are okay, there is a possibility of a SANDBOX system failure.
If you continue to experience similar issues, send feedback to Apple and ask for immediate action.
Other threads in the forum have reported similar symptoms with this iOS 15 beta.
https://developer.apple.com/forums/thread/688416
It is unknown at this time whether it is a phenomenon peculiar to SANDBOX or a bug in Xcode13 and iOS15.
I submitted a feedback to Apple. -> FB9679979
When the delegate of SKRequest and SKProductsRequest is not called, the following log may not be displayed on the Xcode console.
[BackgroundTask] Background Task 8 ("SKProductsRequest"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this.
A report similar to this phenomenon was posted on other sites last month, so I will introduce it.
It seems that it has not been solved yet.
https://github.com/RevenueCat/purchases-ios/issues/851
https://stackoverflow.com/questions/67385235/background-task-9-skreceiptrefreshrequest-was-created-over-30-seconds-ago
The same phenomenon occurred with the sample code for in-app purchase provided by Apple.
Offering, Completing, and Restoring In-App Purchases
https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/offering_completing_and_restoring_in-app_purchases?language=objc
I get the same symptom when I download the sample code, change the product ids for team and in-app purchases to my own, build with Xcode 13 and run it on an iOS 15.0.1 device.
I checked it on multiple devices with iOS 15.0.1, but the same phenomenon occurred.
Is there something wrong with the SANDBOX?
This seems to have been addressed with a bug in WebKit, but it does not seem to be reflected in the official release version of iOS 13.2.This message is also displayed in the official release version of iOS 13.2.https://stackoverflow.com/questions/58321114/why-i-get-the-console-warning-process-kill-returned-unexpected-error-1-when
I am also troubled by this problem.I heard that you used UIStackView. Can you put UIBarButtonItem in UIStackView?The UIBarButtonItem reference states that the button is specialized for the placement of UIToolBar and UITabBar.https://developer.apple.com/documentation/uikit/uibarbuttonitemThe following code I tried didn't work.Please give us advice on what kind of code you have written. // note
UIBarButtonItem *noteButton = [[UIBarButtonItem alloc] initWithBarButtonSystemItem: UIBarButtonSystemItemCompose target:self action:@selector(noteViewAction)];
// camera
UIBarButtonItem *cameraButton = [[UIBarButtonItem alloc] initWithBarButtonSystemItem: UIBarButtonSystemItemCamera target:self action:@selector(cameraViewAction)];
// stackView
UIStackView *stackview;
stackview = [[UIStackView alloc] initWithFrame:CGRectMake(0.0f, 0.0f, 300.0f, 44.0f)];
stackview.axis = UILayoutConstraintAxisHorizontal;
stackview.alignment = UIStackViewAlignmentFill;
stackview.distribution = UIStackViewDistributionFill;
stackview.spacing = 20;
[stackview addArrangedSubview: noteButton.customView];
[stackview addArrangedSubview: cameraButton.customView];
UIBarButtonItem *stackViewBarButtonItem = [[UIBarButtonItem alloc] initWithCustomView:stackview];
self.navigationItem.leftBarButtonItem = stackViewBarButtonItem;
