search

jonbhanson / flutter_native_splash

Automatically generates native code for adding splash screens in Android and iOS. Customize with specific platform, background color and splash image.
https://pub.dev/packages/flutter_native_splash
MIT License
1.28k stars 200 forks source link

When uploading an App to AppStore connect I get "Asset validation failed" #689

Closed kouroku-room closed 1 month ago

kouroku-room commented 1 month ago

Describe the bug

I followed the readme on pub.dev. Then, to release the app, I tried to upload the app from my Mac using the Transporter app. But I get the following error when uploading an App to AppStore connect.

Asset validation failed (90476) Invalid bundle. Because your app supports Multitasking on iPad, you need to include the LaunchScreen.storyboard launch storyboard file in your com.kourokuroom.xxxxxxxxxxxx bundle. Use UILaunchScreen instead if the app’s MinimumOSVersion is 14 or higher and you prefer to configure the launch screen without storyboards. For details, see: https://developer.apple.com/documentation/bundleresources/information_property_list/uilaunchstoryboardname（ID: b5359409-4084-4872-a573-8d21dc093cf4）

Configuration

flutter_native_splash:
  web: false
  color: "#ffd9dc"
  android_12:
    color: "#ffd9dc"
    icon_background_color: "#f6abca"

Device (please complete the following information):

Additional context

I found "stack overflow" page with a similar situation.

https://stackoverflow.com/questions/74794155/invalid-bundle-because-your-app-supports-multitasking-on-ipad-you-need-to-incl

So, I changed the contents of LAUNCH_SCREEN_STORYBOARD from LaunchScreen.storyboard to LaunchScreen as a trial, and this error is no longer displayed.

The value is different from the readme, but is this method still OK?

If it is common to get the same error with the current pub.dev's readme procedure, it would be great if you could add it to the readme so that no one else suffers from the same error!

jonbhanson commented 1 month ago

Hi @kouroku-room, thanks for the report and the solution. This is the first time this error has ever been reported, so I think it is not a common error, at least with Flutter apps. As far as I know, your solution should be fine. Since the problem seems to be resolved for you, I will close this ticket.