[TIMOB-23223] Windows: No splash screen when deploying alloy app to windows 10 mobile
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2016-04-19T18:51:44.000+0000 |
|---|
| Affected Version/s | Release 5.3.0 |
|---|
| Fix Version/s | Release 5.3.0 |
|---|
| Components | Tooling, Windows |
|---|
| Labels | qe-5.3.0 |
|---|
| Reporter | Harry Bryant |
|---|
| Assignee | Feon Sua Xin Miao |
|---|
| Created | 2016-04-15T21:01:48.000+0000 |
|---|
| Updated | 2016-04-25T17:44:50.000+0000 |
|---|
Description
Description
It was found that when deploying an alloy mobile project to a windows 10 mobile device, the splash screen is not present, and instead presents a black screen with a white crossed box in the center. This does not occur for classic projects, or alloy/classic projects on 8.1 devices.
Steps to Reproduce
1. Create an alloy mobile project.
2. In the Command Prompt, cd into project directory.
3. appc run -p windows -T wp-device --wp-sdk 10.0
4. Launch app once built.
Actual Result
No splash screen on launch, white box instead
Expected Result
Splash screen should be present on launch of app.
Attachments
| File | Date | Size |
|---|
| alloy.png | 2016-04-19T14:51:53.000+0000 | 26282 |
| classic.png | 2016-04-19T14:51:53.000+0000 | 15324 |
[~htbryant] Just to confirm: - This happens for Alloy projects on Win 10 mobile? - It doesn't happen for Alloy projects on Win 8.1 mobile? - It doesn't happen for classic projects on Win 8.1 mobile? - It doesn't happen for classic projects on Win 10 mobile?
I believe the white box with an X in it is sort of a "default" splash screen/logo used. I believe it comes from cmake itself: titanium_mobile_windows/cli/vendor/cmake/share/cmake-3.4/Templates/Windows/SplashScreen.png What I don't understand is why that would be used, when in other cases we use the "default" Appcelerator splashes from titanium_mobile_windows/templates/build/Assets
Alloy default splash screen image for windows,
SplashScreen.pngis also a white crossed box, not sure if it's the culprit: https://github.com/appcelerator/alloy/tree/master/platforms/windows/project/app/assets/windows What do you see if you replace<projectdir>\app\assets\windows\SplashScreen.pngwith a different image file? Do you still see the white box?[~fmiao] So I tested this a little too with 5.2.2.GA. If I did a classic ti project for win 10 mobile, it used the default SplashScreen.png from windows SDK (which still isn't quite right in the way it looks visually, I should file a ticket for that). When I ran alloy new on the project and then built, it used the white box with an X in it for the splash screen. So it definitely is coming from alloy. When I build with alloy, during the build process is when I see new image assets copied into the Resources/windows folder. So it looks like if I have no custom splash screen, then with a classic app it falls back to the proper splashes we have as defaults in Windows SDK. If I have none with an alloy app, it uses Alloy's default splash screens for windows. The fix here may be to simply ship fixed/better default splash screens in alloy for Windows.
Additionally, I think because we use the DefaultIcon.png stuff in Windows to generate icons, we probably don't need the Logo/SmallLogo/StoreLogo files.
[~cwilliams] can confirm, This occurs ONLY on alloy projects for windows 10 mobile, it does not affect classic projects, or alloy projects for windows 8.1
Master: https://github.com/appcelerator/alloy/pull/782 1_8_X: https://github.com/appcelerator/alloy/pull/783
Verified as fixed, The splash screen is present. Tested on: Microsoft Lumia 640 (10) Windows Simulator (10) Windows 10 Studio: 4.6.0.201604210304 Ti SDK: 5.3.0.v20160421080259 Appc NPM: 4.2.5-3 App CLI: 5.3.0-36 Node v4.4.3 Closing Ticket.