I just started learning Swift. It's been only a month, and I can assure you that I'm not doing anything fancy. Yet, the launch screen on the simulator is taking a long time to disappear before the app starts. It stays on for at least 5 seconds, and it takes another 2.5 seconds to slowly fade away. And as it fades out, the first view of the app slowly fades in. It was working fine (took only a fraction of a second) until a couple of days ago when this started happening suddenly while I was working on a sample app. Here are things I've confirmed:
During the initial 5 seconds, the app won't accept any user interaction. But during the 2.5 seconds of fading, it responds to touches.
This is a systematic problem because ALL sample code shows the same problem.
Even a new project, without any modifications, shows the same problem. I tried both "Game" and "Single View Application". After the name of the project is displayed as a launch screen, it takes about 8 seconds for the "Hello World" to appear completely. (When "Game" is selected.)
Restarting Xcode and rebooting the Mac do not help.
Updating to Xcode (6.4) does not help. My Xcode was 6.3.x (I believe it was 6.3.2 before the update).
Reinstalling a new copy does not help. I deleted the newly updated 6.4, and re-installed a new copy of 6.4.
The only similar incident I could find was this link, which did not provide the answer.
I was working on a simple practice program. It ran successfully just like it did numerous times before. Then, I made some minor changes to the code (nothing fancy --- just some trivial changes.) And the next time I pressed the RUN button, I noticed that the launch screen took a considerably longer to disappear. After that, it just won't go back to the way it was.
Could someone please advise the cause of the problem and the solution? Thank you very much.
You may have Slow Animations turned on. Go to the simulation and check under Debug:
Related
Im using Magic Leap One: Creator Edition almost everyday for Unity Development, but I stumbled across the following issue:
Magic Leap does not show anything (Menu and icons) when I start magic Leap device. I see the starting screen with and astronaut flying with text TAP TO START. I click, as usual, and it takes around 30-45 seconds to load and everything disappears (No UI/UX of Menu with app icons). Sometimes I get pop up message Scan Area and when I scan it popups with Area Recognized and still nothing happens after scanning. Even after closing all applications and restarting the device, the same issue arises.
What could be the cause? What can I do?
I found the mistake I made. I changed the models for Icon and Portal with unsupported high polygon models from asset store. If you want to avoid this trouble, follow guidelines for icon and portal asset development.
I have an app that's been available in the app store for a few years that uses Core Data. When the app is launched, the user is taken to the app's home screen where a few buttons are shown. Clicking any of the buttons takes the user to another screen that shows data that is loaded from Core Data in a UITableView (each button takes the user to different data). This is basic functionality that's been working in my app just fine the entire time the app's been available.
At some point last year, I noticed that at random times, the data saved in the app sometimes wouldn't load right away. The first time this happened, I clicked one of the buttons and was taken to a blank screen. I went back to the home screen and tried other buttons, and each screen was blank, so I thought all of my data had been wiped somehow. I proceeded to head back to the home screen and just sat there thinking for about 15 seconds, then I clicked one of the buttons again, but this time the data appeared. All of the other screens had data now as well.
I haven't updated the app in quite a while, so my code is unchanged. I don't recall there being a new iOS release around the time I started observing the issue, but it's possible.
This has happened a few more times since I first discovered it (3 or 4 times total over the last 6 months), but there seems to be no pattern at all. Once the data finally loads during these situations, it always loads right away from that point forward. This has made it impossible for me to debug it, because I can't force this situation to happen (99% of the time the data loads immediately).
Has anyone encountered this before, or have any recommendations on how to proceed? I've witnessed this on the Simulator and once on an actual device.
Random delays in updating your UI are a classic sign of attempting to update the UI from outside the main queue. It'll work, usually, but it may be delayed, and the delays won't be consistent. Make sure that when you try to update the UI, you're on the main queue. Use DispatchQueue.main.async() if necessary.
Assuming that you're using Xcode 9, make sure the main thread checker is turned on. That'll help you find this kind of problem when you're running the app from Xcode. Go to the target pop-up at the top of Xcode's window and select "Edit scheme...". In the "Run" section of the window, go to "Diagnostics" and make sure "Main Thread Checker" is turned on.
I'm not sure if I phrased the question properly but I'm getting strange XCode build and run behavior that is frankly too annoying to ignore anymore.
Here's my scenario:
I build and run my XCode project onto my iPhone to play around with. Then I click the square stop button in the toolbar which terminates the app on my device and the stop button turns light grey again. This is then what I see:
I edit some code and then hit play again. Hmm, that's weird, it's not building. Taking a look at the above screenshot I see that even though it looks like it stopped running it still says "running" in the activity viewer. Expanding the little "2" button shows me this:
So that's the problem. I don't know why when I hit stop, everything stops as normal but it still says "running" and isn't starting up again when I hit run again. Now here is the annoying solution I'm working with. To get it running again, first I expand the scheme menu and choose a random simulator device like so:
Then, I simply switch it back to my device like so:
After I do that, the activity viewer automatically starts building the project and launching it on my device as if everything was normal:
It does this almost every time I build and run. It didn't used to do this at all and frankly my patience has run out with it. Am I missing something? How does one solve this without my hack-around? F.Y.I. I'm using XCode 7.1 (7B91b).
I was facing the same issue, i just build the project once when the running condition is showing up and thats it it solves my issue. So i would suggest just ⌘B once.
I'm having a constant issue of particle effects not appearing in the editor. Everything works fine when I first create them, but after some time they stop appearing. I just see the black background, but the particles aren't there.
The only way I'm able to deal with this problem is to delete the node and create a new particle node with the same attributes, which is time consuming and annoying. And then, after a while, the same thing happens to the new particle nodes.
Anyone else experience this?
This happens to me all of time after editing a value and switching to code view of another page. Come back and the preview is gone. Can confirm it is still broken in Xcode 7.3 Beta
There are a couple of home remedies that work until it gets fixed by Apple.
Right click on the file --> Open As --> Quick Look
select a different file and come back and it should work now
or
Close the emitter document with File --> Close “Particle.sks” (Control-Command-W) and reopening it should circumvent the issue.
Hope this helps in the mean time
I am following the Udacity tutorial on Swift, and for some reason when I added the second view, I usually get a black screen (as in the screen print) right when I open the app. Occasionally I get it working but usually not.
What could be the problem?
Noticed that "Did appear" is printed before "Will appear", is that a bug or did I do something wrong?
I have read this and this but it didn't help much. I also have tried several times to clean the project and rebuild it (nothing changed).
One time I just commented out some code (from the second view that should be loaded) and it worked suddenly. When I uncommented the same code it still worked.
Another time it worked when I disconnected the second view on the story board (it was still there, just no way to reach it).
Both have worked at least one time, and not worked many times.
Sorry this seems like I throw in random pieces of information, but I have no idea what could be the reason.