Posts

Post not yet marked as solved
0 Replies
508 Views
I've gotten the following error message a few times, does anyone know anything about it? I currently have a WidgetExtension and am suspecting that this is the circle. Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'ko' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSendMessageIntent in the 'ko' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesIntent in the 'ko' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSendMessageIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards,
Posted Last updated
.
Post not yet marked as solved
0 Replies
281 Views
I had two Widget Extensions, which are visible in the Widget Gallery. But the problem is another Widget Extension that I recently added. I have verified that the Widget Extension works fine in the Simulator, but when I deploy to TestFlight, the third Widget Extension I added is not visible in the Widget Gallery. I've been experimenting with this and have a few suspicions. #1 When I update the app, it doesn't get added to the Widget Gallery, but when I uninstall the app and reinstall the new version, it shows up in the Widget Gallery. This experiment makes me suspect that the new Widget Extension is missing for some reason during the update process. However, the counterpoint to this is that the second Widget Extension was added directly to the Widget Gallery upon update. It's strange that I only get this error when adding the 3rd Widget Extension. #2 This is actually the point that I think is causing it. When I was developing the 3rd Widget, 1 out of 10 times I would get the following log. I've looked around and found people like me who say they don't see it in the Widget Gallery, but I'm confused if this is the real culprit because it only comes up 1 out of 10 times. Also, if this error is the cause, why does uninstalling and reinstalling the app work? SendProcessControlEvent:toPid: encountered an error: Error Domain=com.apple.dt.deviceprocesscontrolservice Code=8 “Failed to show Widget ‘com.example.test.TestWidgets’ error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 “The request to open “com.apple.springboard” failed.” UserInfo={NSLocalizedDescription=The request to open “com.apple.springboard” failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x6000037e0690 {Error Domain=BSServiceConnectionErrorDomain Code=3 “XPC error received on message reply handler” UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}.” UserInfo={NSLocalizedDescription=Failed to show Widget ‘com.mole.godlife.ScheduleWidgets’ error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 “The request to open “com.apple.springboard” failed.” UserInfo={NSLocalizedDescription=The request to open “com.apple.springboard” failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x6000037e0690 {Error Domain=BSServiceConnectionErrorDomain Code=3 “XPC error received on message reply handler” UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}., NSUnderlyingError=0x6000037e0b10 {Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 “The request to open “com.apple.springboard” failed.” UserInfo={NSLocalizedDescription=The request to open “com.apple.springboard” failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x6000037e0690 {Error Domain=BSServiceConnectionErrorDomain Code=3 “XPC error received on message reply handler” UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}}} Domain: DTXMessage Code: 1 User Info: {. DVTErrorCreationDateKey = “2023-10-26 23:19:56 +0000”; } — System Information. macOS Version 14.0 (Build 23A344) Xcode 15.0 (22265) (Build 15A240d) Timestamp: 2023-10-27T08:19:56+09:00 Summarize To summarize, I have 3 Widget Extensions, and the 3rd one is not showing up in the Widget Gallery. I have 2 suspicions as to why this is happening. First, the Widget Extension seems to get lost in the app update process, and second, there is an error message that comes up 1 out of 10 times, and I think that is the cause. I would love to hear your thoughts on this issue and if you need any additional information, I will provide it as soon as possible. Thank you for reading this long post.
Posted Last updated
.