SDK 5.2.0 - LaunchLogo.png 不工作
SDK 5.2.0 - LaunchLogo.png doesn't work
正在尝试让 LaunchLogo.png 正常工作，跟随 this
我的tiapp.xml:
<use-app-thinning>true</use-app-thinning>
<enable-launch-screen-storyboard>true</enable-launch-screen-storyboard>
在 app/assets/iphone 我有所有五个 LaunchLogo*.png。
在项目根目录中我有一个 DefaultIcon.png.
根据文档，启动屏幕将使用 LaunchLogo*.png 而不是 DefaultIcon.png。但是，在 iPad 设备上进行干净的构建和安装后，我会在启动屏幕上看到 DefaultIcon.png。
无法正常工作。任何的想法？谢谢
哦，在发行说明的底部：
iOS Launch Logo Caching Issue
Launch logo updates are not reflected when rebuilding the app. iOS caches launch screens to a PNG file that appears to only be invalidated by restarting the iOS. The following changes have no effect: uninstalling the app, cleaning the Titanium app and rebuilding, and removing the cached image from the hard drive. Upon installing the updated app, it writes a new PNG file to cache of the old launch screen. It appears iOS keeps the cached launch screen in memory despite the app is not running. The only way to show the updated launch logo is to restart the simulator and/or device. Users should see a warning about this issue.
正在尝试让 LaunchLogo.png 正常工作，跟随 this
我的tiapp.xml:
<use-app-thinning>true</use-app-thinning>
<enable-launch-screen-storyboard>true</enable-launch-screen-storyboard>
在 app/assets/iphone 我有所有五个 LaunchLogo*.png。
在项目根目录中我有一个 DefaultIcon.png.
根据文档，启动屏幕将使用 LaunchLogo*.png 而不是 DefaultIcon.png。但是，在 iPad 设备上进行干净的构建和安装后，我会在启动屏幕上看到 DefaultIcon.png。
无法正常工作。任何的想法？谢谢
哦，在发行说明的底部：
iOS Launch Logo Caching Issue
Launch logo updates are not reflected when rebuilding the app. iOS caches launch screens to a PNG file that appears to only be invalidated by restarting the iOS. The following changes have no effect: uninstalling the app, cleaning the Titanium app and rebuilding, and removing the cached image from the hard drive. Upon installing the updated app, it writes a new PNG file to cache of the old launch screen. It appears iOS keeps the cached launch screen in memory despite the app is not running. The only way to show the updated launch logo is to restart the simulator and/or device. Users should see a warning about this issue.