I have an ios app but am trying to add a launch image to the start. I am testing on an old ios 6 phone (which I think is the retina 4.7). I added the launch image in assets catalog like
I then have it mentioned like so:
When I run the app on my iPhone 6 device it has no load screen. What am I missing? I used to have a LaunchScreen.storyboard but I have all these images of the right size made and want to use those.
I've had this issue before and I believe it's a bug with Xcode. It will still be trying to use the LaunchScreen.storyboard file.
Try the following:
Clean your project.
Delete the app from the device/simulator.
Restart Xcode/Simulator and re-run.
See https://stackoverflow.com/a/33698093/5032154 for more info.
IDE: Xcode 9.0
My app has an older launch screen that I want to replace with a new one. Trouble is, none of the changes I make to my Launch Screen.storyboard file will show up in Simulator or on devices unless I erase all content and settings first.
I can't seem to find anything wrong in build settings, but maybe I am missing something.
If you're seeing the old launchscreen before the new one, then I'd say it's normal. It happens to me too. I'm certain that this does not happen in production (app from App Store).
If you just cannot see the image you're trying to show in your launchscreen nib or storyboard, I've posted an answer here: https://stackoverflow.com/a/46398588/3231194
I've updated launch screen on an enterprise app, but it won't update when installed on an iPad with the existing app. I've tried completely deleting the app before installing a new version, but it still launches with the old launch screen image.
I've tried installing the new app on another iPad where this app was never installed and the new launch screen appears as expected. Both iPads run the same iOS v9. The app was built with xCode 7.2
In summary I've tried the following scenarios:
updating existing app (version 1) on iPad A - with a new app (version 2)
iPad A, loads the new app v2 with launch screen from version 1
installed new app (version 2) on iPad B, which never had this app.
iPad B, loads the new app v2 with correct launch screen
then I installed old app version 1 on iPad B
iPad B, now loads the old app v1 with launch screen from version 2
It seems the iPad somehow caches the launch screen from the very fist install regardless which version it is. Deleting the app and reinstalling does not seem to help and it does not look code related as the correct launch screen images was loaded on iPad B
I just had this problem and i found that deleting the app off the device or simulator, then restarting the device or simulator seems to fix the issue.
I found just restarting the device didn't work.
I had tried many kinds of solutions and restart your iPhone is the only way.
In xcode, under Assets.xcassets, I clicked on LaunchImage and then unchecked Universal, checked iPhone, unchecked iPhone, and checked Universal again. Then ran build and it cleared the old image.
Simulators and iPhone caches the launch images.
this can help you
1>Clear the derived data under your developer/xcode folder
2>reset the device by pressing home button and lock button at same time
3>Push your code to device and it will work, if this doesnt work then creat ipa file and install using itunes after resetting the device and it will show the new launch images
The answer by Steve still holds as of iOS 13.2.3, but I wanted to add a few more items just to back up this point that otherwise exceed the restrictions of a comment.
For starters, I did delete the app, restart the device, etc but because this issue occurs when a user updates through the app store, those fixes are simply not viable.
Then, I decided to take more drastic actions within the app to try and remedy this. These actions were taken with TestFlight builds.
In my particular case, the problem stems from a version string that misrepresents the installed version.
Step 1 then was to simply remove the UILabel in question. Re-running the app would still cause the label to appear in the app.
Step 2 then was to create an entirely new LaunchScreen storyboard and set it as seen here:
Launching the app still presents the old launch screen.
This leads me to believe that something in the project structure is the source of the caching, and no reasonable changes to the LaunchScreen by the developer are going to get around this.
Update
The app has been released to the Appstore, and using the official store release, the app presents the correct launch screen.
Solution
Again, thanks to the thread I have referenced above I found a way to solve this issue - name your new image differently from the one there was before in case your new one has the same name as the old one and put it out of the *.xcassets folder to the project directory and reference it in your UIImageView. And that's it.
Just delete app from simulated iPhone home screen.
On iPhone 11 Max version 2-finger click and drag up from outer margin of the iPhone which will bring you to the home screen and exit your simulated app.
Then 2-finger click and hold your app, delete app and close simulator.
Open Xcode and click play button to run your simulation and the launch screen should be updated.
P.S. Deleting Xcode cache and derived data couldn't hurt.
See Rambo's post about the issue. At least on iOS 13 you can clear this cache yourself:
import UIKit
public extension UIApplication {
func clearLaunchScreenCache() {
do {
try FileManager.default.removeItem(atPath: NSHomeDirectory()+"/Library/SplashBoard")
} catch {
print("Failed to delete launch screen cache: \(error)")
}
}
}
In a recent Xcode (6.4?) they enabled the ability to drag multiple images to the simulator window and have them added to the photos app.
(Previous to this, a single dragged image would open in safari, from which you could save it.)
Recently, either in Xcode 7, or I suspect after Xcode 7, I noticed that this functionality is broken. When I drag multiple images to the simulator, it just freezes up, and I have to force quit it.
My current version of Xcode is 7.2. The simulator I'm dragging to is iPhone6 8.4 and iPhone6 9.2.
Does anyone else see this problem/have a solution?
Dragging multiple images (and now also videos) into the simulator window should be working fine. They should all get added to the camera roll. This is working fine for me, and there are no other reports of problems. I suggest you try using the simctl command line to try adding your photos as maybe one (or more) of them are problematic, and that might produce more helpful diagnostics if something is wrong with them.
This is an incompatibility with BetterTouchTool. Quitting BetterTouchTool is not sufficient. BetterTouchTool's accessibility privileges must also be revoked in Security & Privacy.
Upgrading to BetterTouchTool 1.5.2, whose version notes allude to fixing a simulator problem, does not appear to have fixed this issue.
I have an app that was created in a previous version of Xcode. It used to not be universal so it launched in 1x/2x mode on an iPad.
Now we want it to run with universal storyboards and size classes. We have converted the storyboards to size classes and changed the project setting to "Universal". We have set up the constraints and it runs fine on iPhone 6 and 5 flavors. But when we launch on an iPad is launches in 2x Mode automatically.
I can not figure out what is going on.
Can not find anything here or on the googles that speaks to this issue. Everyone seems to have success with the steps I enumerated. One post I found here talks about using a launch file, but I changed our launch file to our main storyboard and it still launches in 2x mode.
Appreciate the help. Let me know if there is any screen shots or more info that would help make things clearer.
EDIT
Adding screen shots for the first comment below.
Edit #2
I wonder if it has something to do with the xibs in the storyboard not updating in the newer Xcode. This project was started long ago and the days before storyboards. All I know is that with the latest update of the beta Xcode it just magically works. So strange.
Problems solved when the latest Xcode Beta came out. Possibly something weird with the xibs since this is an old/converted project that stated before storyboards.