Skip to content

v2.0.2 — splash guidance reframed as opt-in, not prescriptive

Choose a tag to compare

View all tags
@macCesar macCesar released this 19 Apr 01:36
· 24 commits to main since this release
v2.0.2
ea4316e

Reframes the Android splash guidance in `--notes` after real-world feedback. v2.0.1 was too prescriptive and recommended a parent theme (`Theme.Titanium.Light.NoTitle`) that doesn't exist in all Titanium SDK versions — users got build failures when copy-pasting the snippet.

What changed

The splash section in `--notes` is now marked "OPTIONAL, advanced" instead of "RECOMMENDED", leads with "for most apps the default is enough — do nothing", and the template uses a placeholder `@style/YOUR_APP_PARENT_THEME` with explicit instructions to verify the parent theme exists in the user's SDK before using it. Lists `Theme.Titanium.Light.Fullscreen` as known-working in SDK 13.2.0 but tells the user to double-check for their own SDK.

Also adds a pre-flight checklist before modifying tiapp.xml:

  • Verify parent theme exists
  • Check whether your project already has a custom theme (extend, don't override)
  • Test the build succeeds before committing

The `--ios-padding` 4% default from v2.0.1 is preserved.

Impact

If you were following the v2.0.1 guidance and your build failed with `resource style/Theme.Titanium.Light.NoTitle not found`, revert your tiapp.xml change and either:

  1. Skip the custom theme (Titanium default works for most apps, visible flicker is cosmetic)
  2. Use `Theme.Titanium.Light.Fullscreen` as parent (verified in SDK 13.2.0)
  3. Extend your app's existing theme if you already have one
Assets 2
Loading