Status bar could not find cached time string image. Rendering in-process
Asked Answered
A

6

113

I get the above runtime message after I upgraded to Swift4.1 and Xcode 9.3. Before the upgrade I did not have this message in my console window.

Status bar could not find cached time string image. Rendering in-process.

comes up every few minutes as long as I have the App running.

It sees to me there is no negative side effect, my App is running, as usual, I have not seen any problems.

I use the standard Status Bar, have not changed to modify it in any way.

Question 1: Would there be a problem originating from this warning under situations i have not come across yet?

Question 2: Does anyone know how I can get rid of this warning?

Abshier answered 31/3, 2018 at 9:38 Comment(9)
Strange. I am getting this too after upgrading my test device to iOS 11.3 and Xcode 9.3Muliebrity
I'm getting this too, so far it appears to be harmless.Pauiie
Its happening once a minute (for me at least) just after the time rolls over into the new minute.Burmeister
Its happening in my case as well but no issues found till now related to performance etc. It seems like an Xcode bug, going to create a ticket about it BTW. As per my understanding if it is an Xcode bug then it will not create any issues to your project.Outturn
i have the same issue too after updating to swift 4.1Charge
Same to me ;) with Xcode 9.3 and Swift 4.1Slur
same problem with Xcode 9.4 betaHanes
I am running my app on Device (iPhone 6 capacity 16 GB available 5.48 gb) and I have also seen this warning but when I got this message in Xcode console log my app got stuck.Limeade
There's nothing in the message itself to suggest that it's flagging an error or warning condition. More the kind of thing that gets put in to help development, and left in even when it's no longer required.Respiration
C
94

This bug/debug note is present in iOS SDK bundled with Xcode 9.3+

Update: not fixed in Xcode 9.4.1 (9F2000)
Update: not fixed in Xcode 10 (10A255)
Update: not fixed in Xcode 11 betas

I think you can safely ignore it. New versions of iOS/macOS sometimes contain informational debugging messages, and they generally get removed at the next release.

Coatbridge answered 2/5, 2018 at 8:59 Comment(9)
I will wait for the stable release - at least we get this sorted out finally. Thanks for the heads-up.Abshier
This bug is NOT fixed in the 9.4 (9F1027a) releaseJejune
Not fixed in Version 9.4.1 (9F2000)Dorella
@LalKrishna's comment is inaccurate. Just tested with XCode 9.4.1 on iOS 11.3.1 and 11.4, it occurred on both. At least while using a physical iPhone 6Rajasthan
I hope Apple with release Xcode 10 with this kind of error fixed.Welsh
Version 10.0 beta 4, not fixedIden
folks this is most likely an uikit bug (or feature)Oilskin
I don't this is a feature, it should be a debug info. I have edited the answer. Please upvote if you found useful. @AntonTropashkoCoatbridge
I have upvoted long long ago. But am now reconsidering.Oilskin
C
13

Same issue was occurring for me too. To overcome this, I did this

Goto Target -> Deployment Info -> Unchecked 'Hide status bar'

This one resolved my issue. For me, this was the 'Deployment Info' setup.

enter image description here

Cantara answered 6/4, 2018 at 8:57 Comment(12)
I tested with the checked and the unchecked 'Hide status bar' option. Neither option did prevent the message 'Status bar could not find cached ..... ' coming up again every other minute.Abshier
Did you check info.plist is there anything added related to Status Bar?Cantara
I have nothing in the info.plist related to the Status Bar. I am using the default Status Bar.Abshier
Can you plz share, xcode version, and device, in which you r getting this? And also, do ur app supports landscape?Cantara
I am using Xcode 9.3 (9E145) and have this issue when using iPad Air 2 and iPhone 8. Yes the App supports landscape and Portrait orientation.Abshier
Can you please stop orientation once, and check?Cantara
Switched to Portrait only - message still comes back and then switched to Landscape only and message comes back again.Abshier
For me, its coming only if I check ‘Hide status bar’. Let me check with other settings.Cantara
Let us continue this discussion in chat.Abshier
The warning disappear when I have View controller-based status bar appearance set to True in the plistPromptbook
Thanks for the tip but unfortunately this doesn't work for me either. The message come up again.Abshier
Thanks! It worked for me, actually, it was unchecked at first, I checked it and run and then unchecked again and it workedCoan
M
1

I am also seeing this warning appear, and in answer to Question 1, I am also seeing potentially very nasty behaviour associated with it.

Running something close to a basic sample animated triangle Metal app, but with

renderPassDescriptor.colorAttachments[0].loadAction = .load

such that the frame isn't cleared every frame. What seems to be happening is that every other time the warning message is logged, iOS also gets some part of its management of graphics state confused so that I witness a violent flashing of parts of the image (which then goes away again later).

How likely this situation would be to emerge in a 'real' app I'm not sure, but it's definitely not something you want users to end up seeing.

I haven't fixed the problem here thus far; 'Hide status bar' and 'Requires full screen' settings don't help.

Mutz answered 17/4, 2018 at 15:14 Comment(1)
Of course you can;'t fix it. You have your metal state. Apple has it's GLES state for rendeing statusbar and these two apparently collide. File a bug with them proviging a sample app to help them out sort it out on a real world case. This might not surface with vanilla uikit users such as myself.Oilskin
M
1

In my case, it was hiding navigation bare by

self.navigationController?.isNavigationBarHidden = false

When you are hiding the navigation bar, it hides status bar too!. just use

self.navigationController?.navigationBar.isHidden = true

instead. And you will have your status bar back.

Militarist answered 24/9, 2018 at 11:31 Comment(1)
Why does the first line have = false and the second = true? Are you trying to confuse the reader, or is there a purpose. (If there's no purpose, please correct and write true or false on both lines.)Clayborne
O
0

To answer Question 2 drawing upon PeterT answer that addresses Question 1: not only you can not get rid of this warning, but you mustn't, cause it means that the underlying problem is anything, but benign. At least in some scenarious.

This also means that the DEC Field Circus Engineer dance swapping the wheels that flat in meta info for the project would rightfully make you look like a clown.

Oilskin answered 30/7, 2019 at 6:28 Comment(0)
P
-1

I was able to get rid of this warning, by checking the "Requires Full Screen" in Target-> Deployment Info.

Checking this option may have some side-effects in iPad, so you should do it having this in mind.

Palate answered 16/4, 2018 at 15:26 Comment(1)
I am using 'Requires Full Screen' but the message is still coming upAbshier

© 2022 - 2024 — McMap. All rights reserved.