NativeScript / NativeScript/nativescript-cli

The default Nativescript splash screen always loading on real iOS 11 device

Open
#3,159 10 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs os: ios
Dominant language
JavaScript
Stars
1.1k
Forks
204
Avg merge
1d 9h
Merged PRs (30d)
8

Description

From @mutazmq on October 14, 2017 18:33

I'm developing an iOS app but I'm still getting the Nativescript splash screen even though I did the following:

  1. Changed all images in Assets.xcassets folder
  2. Removed iOS platform usingtns platform remove ios and added it again (Just in case there was some caching)
  3. Deleted the app from my iPhone several times

But still I'm getting the same default Nativescript image when the app is launched on my device! However iOS simulator doesn't have this problem and shows me the new image.

Using tns version 3.2.0:

    "tns-android": {
      "version": "3.2.0"
    },
    "tns-ios": {
      "version": "3.2.0"
    }

Copied from original issue: NativeScript/nativescript-angular#1041

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the changed Assets.xcassets with the behavior of tns platform remove ios and re-add ios on a real iOS 11 device versus the simulator. Reproduce the launch flow using NativeScript CLI 3.2.0; done means the customized splash image appears on the physical device rather than the default NativeScript image.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, javascript
Domain
cli, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.