Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-17664] iOS8: Add support for "launch files" in place of images for iOS 8

GitHub Issuen/a
TypeImprovement
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2016-04-25T12:57:40.000+0000
Affected Version/sn/a
Fix Version/sRelease 5.2.0
ComponentsiOS
Labelsios8
ReporterTim Poulsen
AssigneeChee Kiat Ng
Created2014-09-09T20:33:46.000+0000
Updated2016-04-25T12:57:40.000+0000

Description

iOS 8 includes a new feature for XIB-based launch screens that Apple recommends using instead of static images. https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/MobileHIG/LaunchImages.html#//apple_ref/doc/uid/TP40006556-CH22-SW1

Comments

  1. Shannon Hicks 2014-09-09

    +100 this.
  2. Tim Poulsen 2014-09-11

    Perhaps useful info: http://oleb.net/blog/2014/08/replacing-launch-images-with-storyboards/
  3. Ingo Muschenetz 2014-09-11

    We think we may not _need_ this for 3.4.0. If that is determined not to be the case, pull into 3.4.0
  4. Fokke Zandbergen 2014-09-11

    My tests show it looks like having a launch image with the right name convention doesn't work anymore to have iOS recognise apps as being iPhone 6 compatible. It should be easy to just generate an Asset Catalog bundle with the images and a JSON file. Although launch file support will not be needed, I guess we still have to get rid of how the RootViewController is currently simulating a launch screen.
  5. Ygor Lemos 2015-02-05

    Is this planned for the next release?
  6. Tim Poulsen 2015-02-05

    [~ygbr] We're actively investigating better solutions for launch files and icons. I don't know if the changes would be in the next release however. I've linked a bunch of related tickets. Keep an eye on this one and those for updates.
  7. Chee Kiat Ng 2015-08-19

  8. Fokke Zandbergen 2015-08-20

    [~cng] that ticket is only about launch images, which is different from XIB-based launch files.
  9. Hans Knöchel 2016-04-24

    [~skypanther] This feature was exposed in 5.2.0 as part of TIMOB-19694, so can we close this issue?
  10. Tim Poulsen 2016-04-25

    Certainly. Thanks for asking.
  11. Hans Knöchel 2016-04-25

    Closing in favor of TIMOB-19694

JSON Source