[AC-1933] iOS: Ti App xml: fullscreen true - loads wrong splash screen
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-07-10T18:06:41.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Titanium SDK & CLI |
Labels | ios, splash-screen, tiapp.xml |
Reporter | Mads Moller |
Assignee | Mauro Parra-Miranda |
Created | 2013-07-10T12:34:46.000+0000 |
Updated | 2016-03-08T07:40:51.000+0000 |
Description
The default Appcelerator red splash screen is being loaded, when setting fullscreen true in tiapp.xml.
*Steps to reproduce:*
1. Create an app
2. set true
3. place a custom Default.png in the iphone folder
4. build a see the default red splashscreen
Hi Mads, I can't reproduce this unfortunately. I tried both with one of my test projects, and creating a brand new Classic Default Project, both show my custom splash screens fine with fullscreen set to true in tiapp.xml. Tested on iOS 6 simulator with Ti SDK 3.1.0 GA and 3.1.1 GA. Does this only occur on a device by any chance?
hmm.. I had this issue all day, and when I finally changed it into fullscreen false, then I got my custom splash screen back. But now I cannot reproduce either. Im sorry. I might be mental. Ill reopen the issue, if I find the reproducible solution.
Hi Daniel, I can say, it has nothing to do with fullscreen but it happens :S I was just about to publish an app to the App Store, so I did a distribution build. *This is my iPhone folder in my Resources:* !https://dl.dropboxusercontent.com/u/2132088/app-iphone-folder.png! *This is my distribution IPA payload content:* !https://dl.dropboxusercontent.com/u/2132088/app-dist.png! As you see, the default appcelerator images occurs in the final build :S Im not sure of the pattern to reproduce it, but it happens.
Hmm that doesn't sound good. It shouldn't happen at all, so maybe the build scripts are messing up somewhere. So this sometimes happens in your development build? Does it always happen in your distribution build? As a workaround for now so that you can actually submit the app, you can replace the contents at:
Hi Daniel, haha, I hate when stuff is not clear and easy to reproduce. Yes, it happen both in development and distribution. Not each time, but often. (yes i know. It does not make sense). I cannot figure out what is triguring the compiler to use those standard images..