2
votes

I just created an ionic app and previously I added a splash screen and that was working fine. Now I added another splash screen in resources using the command

ionic Cordova resources ios --splash

now when I checked every splash screen in updated.

After I compiled and build the iOS app and tested it shows the previous Splashscreen for a second and then updated splash screen is shown and moved to my home screen.

I removed the platform and added again. reupdated with new splash screen still, this issue exists! WHy does this happen?

3
try using the --force option to ensure the new splash screen is created for all resolutions ionic cordova resources -s --force - jaaaawn
All the resources are updated.I can see that in the splash images in splash folder updated to new. Anyways let me try with --force - user8231819
and you have then rebuild your xcode project? ionic cordova build ios - jaaaawn
Yes.. i run ionic cordova build ios --prod - user8231819
@jaaaawn I tried --force.. still old splashcreen is shown for a second before the new splashscreen - user8231819

3 Answers

17
votes

Finally got the solution.

  1. Delete your app from the device
  2. Power down the device
  3. Power up the device, install and launch the app.

It's not my app issue. I think it wont happen in production version.

3
votes

iOS devices first show a launch image and then the actual splash image from the plugin. The image is the same, so you won't notice this.

But the launch image is cached by the devices and simulators, so if you change the splash image, it will still show the old launch image.

The solution is just to delete the app (no need to power off and on again), and it won't happen in production versions.

1
votes

For all future developers facing this issue since I see no post with the correct solution:

There is a folder that for me was called res/screen/ios which contained the old splash screen and I never replaced that file. Removing the file in that folder from my application, adding the new image in that folder, and changing the name of the new image to 'Default@2x~universal~anyany.png' resolved this issue.