[SWIFT] ITMS-90626 Error Resolution

** ITMS-90626 Error Resolution **

■ Problem

ITMS-90626 error occurred after uploading binaries to AppStore Connect.

• The upload itself was successful, but I received an email notification. (Environment: XCode 12.2 / macOS Catalina)

◇ Actual error content

ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: ja

## ■ Cause
 Upon examination, it seems that the addition of the Widget Kit added from iOS 14 had an effect.

 If you think that Siri related errors are strange even though you should not have implemented Siri
 In the wizard when adding WidgetKit to the target, when Configuration was enabled and created, Siri Intent Definition was automatically created.

 This error was a warning because the created Siri Intent Definition (* .intentdefinition file) was not localized.

 ![スクリーンショット 2020-12-15 16.38.31.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/51578/ebe85559-c66f-6c72-284f-b4dc3f39fafa.png)

## ■ Countermeasures
 This time, I didn't use this Siri Intent Definition consciously, but since Configuration Intent has appeared in the code on the Widget side, it can not be simply removed from the target, so I added localization of Siri Intent Definition. It corresponded by doing.

 ![スクリーンショット 2020-12-15 17.16.40 2.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/51578/cf36b9da-7e57-2daa-1062-ca6a07308ec4.png)

 However, if you think about it carefully, the app that has already added the widget function has already been released, and this error did not occur until the last time.
 If the features added in this update are relevant,
 I want to get the persistence data on the application side on the widget side,
 Since App Groups has been added so that UserDefaults can be linked,
 That may be relevant.

 * Since it is a topic of localization, I think that it is a problem that will become apparent directly when it is translated into Japanese or multilingual, but since it was handled before the previous time, it seems that it is not the reason for the error that appeared at this timing.
 Well, I wonder if the check mechanism on the Apple side was done at this timing.